> 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/co-simulation/co-simulation-with-orchestra/understand-the-orchestra-architecture.md).

# Understand the Orchestra Architecture

## Introduction

Before configuring an Orchestra co-simulation, understand the relationship between the Framework, domains, External Components, and data items.

## Framework

The RT-LAB model acts as the **Orchestra Framework**.

The Framework provides the data communication layer connecting the independently developed simulation components. It can contain only the infrastructure necessary for co-simulation or can also contain functional simulation content.

Conceptually:

**External Component A ↔ Framework ↔ External Component B**

The external components do not need to share their internal implementation with one another. Orchestra is data-centered, and the components exchange named data through the Framework.

## External Components

An **External Component** is a simulation model or application that connects to an Orchestra domain.

The main component types are:

* C-code applications; and
* Simulink models.

## Domains

A **domain** is a logical communication space containing the data exchanged between the Framework and participating External Components.

Each domain has:

* a unique name;
* a Publish set;
* a Subscribe set;
* synchronization settings; and
* connection settings.

Domain boundaries also provide namespace isolation. Data item names must be unique within a domain. However, equivalent components can reuse the same signal names in different domains because the names are not visible from one domain to another.

This makes separate domains useful for repeated or independent component instances.

## Data items

A **data item** represents a signal exchanged within a domain.

Each item is defined by:

* name;
* type; and
* length.

An optional description can also be provided. Subscribe items can additionally have a default value where supported.

Data-item names are case-sensitive, trimmed of leading and trailing spaces, limited to 64 characters after trimming, and cannot contain `,` or `#`.

## Publish and Subscribe

The Publish and Subscribe sets are defined from the Framework perspective.

### Publish

The **Publish set** contains values written by the Framework and consumed by External Components.

### Subscribe

The **Subscribe set** contains values produced by External Components and consumed by the Framework.&#x20;

For example, consider a vehicle simulation in which an External Component calculates the vehicle position and RT-LAB calculates the wheel torque.

| Signal                     | DDF set   |
| -------------------------- | --------- |
| Wheel torque from RT-LAB   | Publish   |
| Vehicle position to RT-LAB | Subscribe |

From the External Component's perspective, it subscribes to `WheelTorque` and publishes `VehiclePosition`.


---

# 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/co-simulation/co-simulation-with-orchestra/understand-the-orchestra-architecture.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.
