> 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/pe-add-on-opal-rt/model-in-schematic-editor/design-the-ehs-circuit/create-subsystems.md).

# Create Subsystems

Subsystems are used in the creation of block diagrams to nest assembled items within other circuits or models.

## Create a subsystem

1. From the **Library Browser > System**, drag a **Subsystem** block into the work area.
2. Double-click the Subsystem to open it. A new canvas appears, representing the subsystem (child level), where you can build your model or circuit. Blocks and connections can be copied and pasted between parent and child levels.
3. To interface with the parent model, use **Power Port** blocks:
   * Power Ports inside the subsystem represent its **inputs**
   * Port numbering defines the mapping between parent and child levels (matching numbers indicate connected signals)

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FzvMX0Fd6McQZ7KeEcO9T%2FcreatingConnectingSubFromSelec.gif?alt=media&amp;token=996df9d5-fd4c-4f8a-8502-87123a0d9e20" alt=""><figcaption></figcaption></figure>

In the **Parameters Sidebar**, you can rename the Subsystem block and optionally add an image to improve clarity and documentation.

You may also adjust the **port locations** to better match your design and improve readability.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2Fq2OSWk4GTtAYFo5cAxxX%2FcreatingConnectingSubDragPort2%20(1).gif?alt=media&amp;token=d03c0a9a-75ab-48db-8e4d-81d66179dd6e" alt="" width="548"><figcaption></figcaption></figure>

## Browse circuits and subsystems

Use the **Model Browser** to expand the top‑level folder and navigate through its nested subsystems (e.g., *MyModel* → *child1* → *child2* → *child3*).

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FrTkT42rA4KhVtrwNVrrj%2Fimage.png?alt=media&amp;token=26797beb-c7be-4454-82d9-6653780f27db" alt=""><figcaption></figcaption></figure>

The **Model Browser** can also be opened from the **Navigation Bar**. The Navigation Bar displays the path from the top model to the active subsystem and allows quick navigation to parent or sibling subsystems by clicking any element in the path or using the arrow menu.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FmVnVAT10ngrCPxwaxNCH%2Fbreadcrumbs.gif?alt=media&amp;token=062d705d-746c-4d55-b5e1-96b620d3ba48" alt="" width="447"><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/pe-add-on-opal-rt/model-in-schematic-editor/design-the-ehs-circuit/create-subsystems.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.
