> 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/system-description-document.md).

# System Description Document

### USB Key <a href="#usb-key" id="usb-key"></a>

At the back of the USB key, you will find a **label** of your **project number** (CC-000000).

The USB key includes the following\*:

* Your project **System Description Document** (SDD, [see below](https://opal-rt.atlassian.net/wiki/spaces/PGetStarted/pages/1230307621/Unbox+your+System#System-Description-Document-\(SDD\))).
  * The System Description Document is a PDF file containing all the specific information about **YOUR product.**
  * As all systems we deliver are different, this is the **main reference** to **your SPECIFIC system.**
* License files for your software (RT-LAB or HYPERSIM)
* Test models
* Test reports
* Other documents or files related to your system

*\* As each system is different, the USB key content may vary.*

We recommend **copying the content of this key** on your computer or on your network and share its content with all the users of your system.

<figure><img src="https://740610027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj2yPoOexc0GyyXlPhHQw%2Fuploads%2FjoB0hv6rGi0V62BiONEs%2Fimage.png?alt=media&amp;token=20f7498c-caa5-4312-90d3-48d539857cfc" alt=""><figcaption></figcaption></figure>

#### System Description Document (SDD) <a href="#system-description-document-sdd" id="system-description-document-sdd"></a>

**The System Description Document is the main reference document for your system. Please, get familiar with its content BEFORE using your system.**

You will find your System Description Document in the “**System\_Documentation**” folder on the USB key (see below).

In this document, you will find, among other information\*:

* A system overview of your system(s)
* Your OPAL-RTLinux and IPMI login credentials
* The technical specifications for your system(s)
* Your specific configurations
* Bitstream description and configuration
* I/Os mapping
* Third-party hardware

*\* As each system is different, the System Description Document content may vary.*

&#x20;

<figure><img src="https://740610027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj2yPoOexc0GyyXlPhHQw%2Fuploads%2FX5LJ480I5e1GEdhGaqVO%2Fimage.png?alt=media&amp;token=3e903800-a63f-4032-865f-7d91fb81bbfb" alt=""><figcaption></figcaption></figure>

#### Other Documents and Files on the USB Key <a href="#other-documents-and-files-on-the-usb-key" id="other-documents-and-files-on-the-usb-key"></a>

Depending on your system, the USB key may include the following documents and files. Documents and files will vary depending on your system.

* **Integration test reports**: these are factory tests and results that were performed on each of the hardware in your order to ensure its proper working condition.
* **Test models**: these are the RT-LAB or HYPERSIM models used to test your specific hardware. You can run the models to verify that your hardware in working as expected.
* **Software licenses**: these are a copy of your target licenses for RT-LAB or HYPERSIM. The software in your order is already installed on your targets and licenses are installed and active.

&#x20;

<figure><img src="https://740610027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj2yPoOexc0GyyXlPhHQw%2Fuploads%2F3QtknxZ6Nv6yD9iTNSEB%2Fimage.png?alt=media&amp;token=5ee63682-589d-4f24-9c00-0df6c53164e6" alt=""><figcaption></figcaption></figure>

&#x20;


---

# 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/system-description-document.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.
