> 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/licensing-reference/workstation-license.md).

# Workstation License

In most cases, a workstation license is **not** required to compile and run simulations on a simulator. The license must be installed on the simulator itself. Once installed, any number of workstations can connect to the simulator to compile or execute real-time simulations.

For certain specific use cases, however, a **workstation license** is required. This includes, for example, using the ePHASORSIM block from the RT-LAB toolbox, certain features of the ARTEMIS toolbox, and others.

## **View the Workstation License Details**

To view the license information, [RT-LAB must be installed on your workstation](https://www.opal-rt.com/docs/rt-lab/get-started/download-and-install-rt-lab.md).

1. In the RT-LAB Project Explorer, click the **Filter targets** icon.
2. In the pop-up window, check **Use filter**, then check **Show 'localhost' target**, then click **OK**.
3. In the Project Explorer, double-click **localhost** under **Targets**.
4. Open the **License** tab.
5. Check the **RT-LAB License Features** list.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-bd9d52e42d150cdb326d53a1d4b39f227d660e7d%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

License features can be either binary (enabled or disabled) or numeric, indicating the number of units available for that feature.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ef356591cd5b180df8f2020d13f84cb3bfb83e0d%2Frtlab-list-licence-target.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Current License Overview** on the right displays information such as the **License Number**, the **Target Number** (corresponding to the workstation’s hard drive serial number), the **Expiration Date**, and the **End of Maintenance Date** are indicated.

* The **Expiration Date** is set to *INFINITY*, unless a demo license is installed.
* The **End of Maintenance Date** indicates how long the workstation is covered by OPAL-RT Support and provides a general cutoff for compatible RT-LAB versions.\
  For example, an **End of Maintenance Date** of *October 5, 2025* means that:
  * You can contact OPAL-RT Support through the [customer portal ](https://opal-rt.com/contact-technical-support/)until October 5, 2025.
  * RT-LAB versions released in 2026 or later will not be supported with this license.

{% hint style="danger" %}
Long Term Support (LTS) versions of 2024.1 and 2024.4 continue to receive updates for customers under maintenance. Therefore, you may not be eligible to use these versions even if your maintenance extends beyond 2024, because new releases for these LTS branches are still being issued after 2024.
{% endhint %}

You can renew the Maintenance Contract by contacting your OPAL-RT representative.


---

# 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/licensing-reference/workstation-license.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.
