> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/getting-started/4.-visualizing-and-using-data/create-a-digital-twin.md).
# Create a Digital Twin
{% hint style="info" %}
The full documentation can be found in the chapter [↗ Digital Twin](/collection/platform/photoreal-twin.md)
{% endhint %}
1. Click Digital Twin **\[A]**\
▷ The Digital Twin overview opens **\[A1]**
2. Click **\[B]**\
▷ The window **\[C]** opens
3. Give the Digital Twin a name in **\[C1]**
4. Optional: In **\[A]**, specify a parent asset. In this case, only assets that are subordinate to this parent asset can be used.
5. Click **\[C3]**\
▷ The Digital Twin is created and opened **\[D]**
## Add an Image
Prerequisite: You are in a Digital Twin **\[D]**
1. Click **\[D1]**\
▷ The window **\[E]** opens.
2. Click **\[E1]** to upload an image or drop an image there via [↗ Drag'n'Drop](https://doc.eliona.io/collection/foreword/user-interface-elements#dragn-drop).
3. The image is uploaded **\[E2]**
4. The image appears in the Digital Twin
## Link a Value
Prerequisite: You are in a Digital Twin **\[D]**
1. Click **\[D1]**
2. On the canvas, click the location where the link should appear.\
▷ A link **\[D2]** appears.
3. Right-click ⚠ Do not skip this step! If you do not right-click, every subsequent click will generate a new link!
4. Left-click on the link **\[D2]**\
▷ The sidebar opens
5. In **\[D3]**, select the value that should be displayed in the link.
6. In **\[D4]**, select the color in which the link will be displayed
7. Optional: In **\[D5]**, enable a reference point.\
▷ You can move the reference point via Drag'n'Drop in the image
8. Optional: Enable a title for the link with **\[D6]**.
---
# 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://docs.buildings.ability.abb/collection/getting-started/4.-visualizing-and-using-data/create-a-digital-twin.md?ask=&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.
