> 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/library-blocks-reference/system-blocks/subsystem.md).

# Subsystem

## Description

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FA2TJFj4bBlFbGhWfJWNm%2Fimage.png?alt=media&amp;token=2162955e-7228-4627-98a7-3e8e13555915" alt="" width="104"><figcaption></figcaption></figure>

The **Subsystem** block organizes a section of a circuit into a separate embedded subsystem, simplifying design, reuse, and maintenance.

{% hint style="info" %}
This block is only available in the eHS library.
{% endhint %}

## Parameters

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2Fc5UE19wFOz8oo2F0eJWK%2Fimage.png?alt=media&amp;token=9cc7b5ec-e8f6-417a-af07-2e8dcfbea297" alt=""><figcaption></figcaption></figure>

| Parameter            | Description                                                                                                                                                                                                                       |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Import Image**     | Allows the uploading of an image on the subsystem. The image can be deleted using the trash can icon.                                                                                                                             |
| **Image Fill**       | <p>Two options<br><strong>Fit:</strong> Preserves image ratio, and fills remaining space with white space.<br><strong>Stretch:</strong> Fills whole subsystem space, stretching the image to whatever shape the subsystem is.</p> |
| **Subsystem border** | On image addition, toggle to show a border around the subsystem or hide it.                                                                                                                                                       |

## Conserving ports

The **Subsystem** block exposes one conserving port for each **Power Port** defined inside the subsystem block. The number and configuration of these ports therefore depend on the embedded subsystem circuit design. For more information, refer to [Create Subsystem](https://github.com/Opal-RT-Technologies/product-docs-ehs/blob/main/model-and-simulation/design-the-power-electric-circuit/create-subsystems.md).

Conserving ports can also be created automatically by connecting a wire from a block inside the subsystem to its boundary.


---

# 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/library-blocks-reference/system-blocks/subsystem.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.
