> 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/glossary.md).

# Glossary

## Hardware and Platforms <a href="#hardware-and-platforms" id="hardware-and-platforms"></a>

<table><thead><tr><th width="170.125">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>simulator</strong></td><td>Hardware platform with a real-time simulation runtime environment.</td></tr><tr><td><strong>workstation</strong></td><td>Computer used to develop, configure, compile, and supervise real‑time simulation models executed on an OPAL‑RT simulator.</td></tr><tr><td><strong>localhost</strong></td><td>Network hostname that refers to the local machine on which a process or service is running.</td></tr><tr><td><strong>expansion unit</strong></td><td>External unit providing additional I/O and FPGA processing.</td></tr><tr><td><strong>board ID</strong></td><td>Identifier of an internal FPGA or I/O board.</td></tr><tr><td><strong>chassis index</strong></td><td>Network address (00–FF HEX / 0–255 DEC) identifying a simulator chassis.</td></tr><tr><td><strong>connector kit</strong></td><td>I/O connector set (e.g., RS‑422, fiber optic).</td></tr><tr><td><strong>DB37</strong></td><td>37‑pin D‑sub connector for analog and digital I/O.</td></tr><tr><td><strong>Small Form‑factor Pluggable (SFP)</strong></td><td>Compact, hot‑swappable transceiver module.</td></tr><tr><td><strong>Power Supply Unit (PSU)</strong></td><td>Power supply module of a system.</td></tr><tr><td><strong>Power Management Unit (PMU)</strong></td><td>Hardware subsystem managing power to embedded components.</td></tr><tr><td><strong>unit</strong></td><td>Generic term for a simulator or expansion unit.</td></tr><tr><td><strong>HIL2GO</strong></td><td>HIL2GO bundle.</td></tr><tr><td><strong>Slot</strong></td><td>In the context of I/O hardware positioning: Lateral position of an I/O module within the unit, from left to right, identified by a number (1, 2, 3, etc.).</td></tr><tr><td><strong>Module</strong></td><td>In the context of I/O hardware positioning: Letter (A, B, etc.) used with the slot number to identify the physical position of an I/O module within the unit.</td></tr><tr><td><strong>Section</strong></td><td>In the context of I/O hardware positioning: Physical grouping of I/O channels within a module.</td></tr><tr><td><strong>Group</strong></td><td>In the context of I/O hardware positioning: Combination of a slot number and module letter, for example, <strong>1A</strong> or <strong>2B</strong>.</td></tr></tbody></table>

***

## Analog and digital I/O <a href="#analog-and-digital-io" id="analog-and-digital-io"></a>

<table><thead><tr><th width="199.5">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Analog Input (AI)</strong></td><td>Analog signal input channel.</td></tr><tr><td><strong>Analog Output (AO)</strong></td><td>Analog signal output channel.</td></tr><tr><td><strong>Digital Input (DI)</strong></td><td>Digital signal input channel.</td></tr><tr><td><strong>Digital Output (DO)</strong></td><td>Digital signal output channel.</td></tr><tr><td><strong>Selectable Digital Input‑Output (SDIO)</strong></td><td>Digital channel configurable as input or output.</td></tr><tr><td><strong>I/O</strong></td><td>Input Output.</td></tr><tr><td><strong>I/O channel</strong></td><td>Individual physical or logical I/O connection.</td></tr><tr><td><strong>I/O interface</strong></td><td>Communication layer enabling data exchange between a system and external devices.</td></tr><tr><td><strong>I/O module</strong></td><td>Hardware component performing I/O operations.</td></tr></tbody></table>

***

## Software, Toolboxes, and Platforms <a href="#software-toolboxes-and-platforms" id="software-toolboxes-and-platforms"></a>

<table><thead><tr><th width="149.5">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>RT‑LAB</strong></td><td>real‑time simulation platform used to configure, execute, and control distributed real‑time simulations on OPAL‑RT simulators.</td></tr><tr><td><strong>HYPERSIM</strong></td><td>real‑time simulation platform used to configure, execute, and control distributed real‑time simulations on OPAL‑RT simulators.</td></tr><tr><td><strong>ARTEMiS</strong></td><td>CPU‑based electrical simulation toolbox.</td></tr><tr><td><strong>eFPGASIM</strong></td><td>FPGA‑based power electronics simulation toolbox.</td></tr><tr><td><strong>eHS</strong></td><td>FPGA‑based electric hardware solver provided with eFPGASIM toolbox</td></tr><tr><td><strong>ePHASORSIM</strong></td><td>phasor/RMS‑domain solver for large‑scale power system simulation.</td></tr><tr><td><strong>RT‑EVENTS</strong></td><td>Real‑Time Events Simulation Toolbox.</td></tr><tr><td><strong>RT‑XSG</strong></td><td>FPGA‑based I/O and communication toolbox.</td></tr><tr><td><strong>toolbox</strong></td><td>Collection of functions, tools, and blocks for a technical domain.</td></tr><tr><td><strong>Orchestra</strong></td><td>Co‑Simulation toolbox.</td></tr><tr><td><strong>4DV‑SIM</strong></td><td>Autonomous system testing platform.</td></tr><tr><td><strong>Dashboards</strong></td><td>OPAL‑RT dashboards application for visualization and interaction.</td></tr><tr><td><strong>EXata CPS</strong></td><td>Communication network emulation solution for HYPERSIM and RT-LAB.</td></tr><tr><td><strong>OPAL‑RTLinux</strong></td><td>OPAL‑RT real‑time operating system.</td></tr><tr><td><strong>Schematic Editor</strong></td><td>Graphical editor for building electric circuit models for the eHS solver.</td></tr><tr><td><strong>ScopeView</strong></td><td>Graph and data processing software.</td></tr><tr><td><strong>TestView</strong></td><td>Test automation and analysis software.</td></tr><tr><td><strong>SPS Software</strong></td><td>Power systems modeling software formerly known as SimPowerSystems.</td></tr></tbody></table>

***

## Modeling, Simulation Concepts, and Standards <a href="#modeling-simulation-concepts-and-standards" id="modeling-simulation-concepts-and-standards"></a>

<table><thead><tr><th width="200.125">Preferred Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Modelica</strong></td><td>Object‑oriented, declarative, multi‑domain modeling language.</td></tr><tr><td><strong>S‑Function</strong></td><td>User‑defined Simulink® block written in C, C++, Fortran, or MATLAB®.</td></tr><tr><td><strong>Functional Mock‑up Interface (FMI)</strong></td><td>Standardized interface enabling model exchange and co‑simulation.</td></tr><tr><td><strong>Functional Mock‑up Unit (FMU)</strong></td><td>ZIP file containing compiled model and FMI metadata.</td></tr><tr><td><strong>Co‑simulation</strong></td><td>Technique allowing multiple simulators to exchange data during execution.</td></tr><tr><td><strong>time step</strong></td><td>Simulation execution interval.</td></tr><tr><td><strong>connectable point</strong></td><td>Logical or graphical interface element that can be connected to exchange signals or data between components.</td></tr><tr><td><strong>data point</strong></td><td>Individual piece of data or signal value associated with a connectable point during simulation or execution.</td></tr></tbody></table>

***

## Simulation Levels and Testing <a href="#simulation-levels-and-testing" id="simulation-levels-and-testing"></a>

| Preferred Term                        | Definition                                           |
| ------------------------------------- | ---------------------------------------------------- |
| **Model‑in‑the‑Loop (MIL)**           | Model executed without real hardware.                |
| **Software‑in‑the‑Loop (SIL)**        | Software executed without real hardware.             |
| **Hardware‑in‑the‑Loop (HIL)**        | Real hardware tested with simulated environment.     |
| **Power Hardware‑in‑the‑Loop (PHIL)** | HIL involving real power exchange.                   |
| **Rapid Control Prototyping (RCP)**   | Rapid development and testing of control algorithms. |
| **Test Bench**                        | Controlled setup for system or component evaluation. |
| **Device Under Test (DUT)**           | Hardware or software being tested.                   |

***

## Networking and Infrastructure <a href="#networking-and-infrastructure" id="networking-and-infrastructure"></a>

<table><thead><tr><th width="229.5">Preferred Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Local Area Network (LAN)</strong></td><td>Local network connecting devices in a limited area.</td></tr><tr><td><strong>localhost</strong></td><td>Hostname referring to the current machine.</td></tr><tr><td><strong>Target I/O Interface</strong></td><td>Interface connecting the simulator to external hardware devices.</td></tr><tr><td><strong>Workstation</strong></td><td>Computer used to develop and supervise simulations.</td></tr></tbody></table>

***

## Electrical and Power Systems <a href="#electrical-and-power-systems" id="electrical-and-power-systems"></a>

| Term                                            | Definition                                                            |
| ----------------------------------------------- | --------------------------------------------------------------------- |
| **Electromagnetic Transient (EMT)**             | Fast electrical transient phenomena.                                  |
| **Electromagnetic Interference (EMI)**          | Electromagnetic disturbance affecting circuits.                       |
| **Distributed Parameter Line (DPL)**            | N‑phase distributed parameter line model.                             |
| **Modular Multilevel Converter (MMC)**          | FPGA‑based MMC simulation toolbox.                                    |
| **Sine Triangle Pulse Width Modulation (SPWM)** | PWM modulation technique using sine and triangle waves.               |
| **Intelligent Electronic Device (IED)**         | Intelligent Electronic Device used in power systems.                  |
| **per unit (pu)**                               | Dimensionless quantity expressed relative to a defined base quantity. |

***

## System Architecture and Miscellaneous <a href="#system-architecture-and-miscellaneous" id="system-architecture-and-miscellaneous"></a>

| Term                                  | Definition                                               |
| ------------------------------------- | -------------------------------------------------------- |
| **System**                            | One or more units with supporting hardware and software. |
| **System Description Document (SDD)** | Authoritative system definition document.                |
| **Setpoint (SP)**                     | Target value for a control variable.                     |
| **Power ON**                          | Powered state where system is on.                        |
| **Power OFF**                         | Powered state where system is off.                       |


---

# 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/glossary.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.
