> 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-pss-e-model/add-more-native-components.md).

# Add More Native Components

When possible, changes are better made in the original source data before import. However, depending on the source format and the available import mappings, some modifications may be difficult to implement or may not be supported directly.

To address this limitation, the Excel configuration file can be used to **augment an imported model** by adding new components that are not present in the original network data.

## Typical use cases

The Excel Template can be used to add components such as:

* Additional loads
* Current sources
* Voltage sources
* Faults
* FMU-based components
* Custom control elements
* Additional buses required by newly added components

## Connect additional components to buses

{% stepper %}
{% step %}

### Open the Excel configuration file

Open the Excel configuration file saved in your model directory.
{% endstep %}

{% step %}

### Configure the additional components

The Excel Template contains worksheets for all supported Native Library components. Navigate to the worksheet corresponding to the component you want to add and configure its parameters as described in the [Native Library Components](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components.md) documentation.
{% endstep %}

{% step %}

### Attach the components to network buses

To connect the new component to the imported network, specify the **component identifier** of the target bus in the component's **Bus** parameter.

The bus identifier must exactly match the identifier generated during the import process. This allows ePHASORSIM to merge the component defined in the Excel Template with the imported network model.

You may also attach a component to additional buses using the **Bus** worksheet. To do so:

1. Add a new bus entry in the **Bus** worksheet.
2. Define a unique bus identifier in the **ID** parameter.
3. Use this identifier in the **Bus** parameter of any component that should be connected to the new bus.

To become part of the imported network, the new bus must be electrically connected to an existing bus through a suitable network component, such as a line, transformer, cable, or switch. Otherwise, the bus will remain isolated from the network.
{% endstep %}
{% endstepper %}

## Limitations

It is **not** currently possible to:

* Remove imported components
* Modify parameters of imported components
* Replace imported components directly through the Excel Template

Any modifications to existing imported components must be performed in the original source model before import.


---

# 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-pss-e-model/add-more-native-components.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.
