> 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/english-v14/documentation/assets/ein-asset-konfigurieren.md).

# Configure an asset

Proceed as follows to modify an asset.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/vv4miGTjyKRf3Lc7NCDm/763F6A5E-494E-4311-92B9-8F8DE4189942.png" alt=""><figcaption><p>Fig. 1 - The Asset menu with the asset list</p></figcaption></figure></div>

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/KupRRyCR9muKVVQ7mC9m/55B2AC04-CC63-4033-81E8-E526721E5641.png" alt=""><figcaption><p>Fig. 2 – The "Asset details" This window is <a href="/collection/english-v14/documentation/assets/asset-details.md">-> here</a> explained in detail</p></figcaption></figure></div>

## Open asset settings

1. Click in the menu bar on **Assets \[A]**\
   ▷ The "Assets" menu with the **asset list \[C]** appears
2. Click on the name of the asset you want to configure **\[B]**\
   ▷ The ↗ [asset details](/collection/english-v14/documentation/assets/asset-details.md) open (Fig. 2)
3. Make sure that you are in the tab **General \[D]** are
4. Click on **\[E]**\
   ▷ The asset settings (Fig. 3) open
5. Configure the available settings as desired.

## Available settings

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/1G3wGEciiKJtUOnBZjXu/Charakteristics%20(2).png" alt=""><figcaption><p>Fig. 3 – The asset settings</p></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="119.33333333333331">Icon</th><th width="205">Description</th><th>Details</th></tr></thead><tbody><tr><td><strong>[H]</strong></td><td>GAI</td><td>Click to <a href="/collection/english-v14/preface/glossar.md#gai">↗ GAI</a> adjust</td></tr><tr><td><strong>[I]</strong></td><td>Name</td><td>Click to adjust the name of the asset</td></tr><tr><td><strong>[J]</strong></td><td>Description</td><td>Click to adjust the description of the asset</td></tr><tr><td><strong>[K]</strong></td><td>Asset type</td><td>The asset type cannot be changed in this field. Click <a href="#asset-typ-aendern">↗ here</a>, to learn how to change the asset type</td></tr><tr><td><strong>[L]</strong></td><td>project</td><td>Shows the project</td></tr><tr><td><strong>[M]</strong></td><td>External ID</td><td>Here you can specify one or more external IDs of the asset.</td></tr><tr><td><strong>[N]</strong></td><td>Augmented Reality</td><td>Check the box to enable this asset for<a href="/collection/english-v14/documentation/weitere-funktionen/augmented-reality.md"> ↗ Augmented Reality</a> .<br><strong>⚠ Warning</strong>: This process costs Infravolt!</td></tr><tr><td><strong>[O]</strong></td><td>Tracker</td><td>Here you can select a <a href="/collection/english-v14/documentation/weitere-funktionen/tracking.md">↗ Tracker</a> that is assigned to or attached to the asset.</td></tr><tr><td><strong>[P]</strong></td><td>Parent location</td><td>Click to adjust the parent location of the asset</td></tr><tr><td><strong>[Q]</strong></td><td>Parent asset</td><td>Click to adjust the parent asset</td></tr><tr><td><strong>[R]</strong></td><td>Location</td><td>Click to place the asset on the <a href="/collection/english-v14/documentation/widgets/vordefinierte-widgets/karte.md">↗ map</a> to place.<br>◈ More information about this function can be found in the chapter <a href="/collection/english-v14/documentation/assets/assets-auf-einer-karte-platzieren.md">↗ Place assets on a map</a>.</td></tr><tr><td><strong>[S1]</strong></td><td>Activate/deactivate asset status</td><td>Tick the box to <a href="/collection/english-v14/documentation/assets/asset-status-aktive-inaktive-nicht-uberwachte-assets.md">↗ Asset status</a> activate/deactivate the function.<br>◈ The asset status indicates whether an asset is displayed as "Active", "Inactive" or "Not Monitored".<br>◈ We recommend not setting a value below 5 minutes or 300 seconds. <a href="/collection/english-v14/documentation/assets/asset-status-aktive-inaktive-nicht-uberwachte-assets.md#minimales-zeitintervall">↗ More information</a></td></tr><tr><td><strong>[S2]</strong></td><td>Asset Status: Value</td><td>Enter a numeric value here</td></tr><tr><td><strong>[S3]</strong></td><td>Asset Status: Unit</td><td>Choose whether the value entered under <strong>[R1]</strong> should refer to seconds, minutes or hours.</td></tr><tr><td><strong>[T]</strong></td><td>Tags</td><td>Assign <a href="/collection/english-v14/documentation/tags.md">↗ Tags</a> to</td></tr><tr><td><strong>[U1]</strong></td><td>Asset characteristics</td><td>Here you can view the categories of the<a href="broken://pages/cb1cd8d93c2e69c36d452959a75a8ec501af8f4b#schritt-2-dem-asset-template-charakteristiken-hinzufugen"> ↗ asset characteristics</a> defined in asset modeling.</td></tr><tr><td><strong>[U2]</strong></td><td>Asset characteristics: Value</td><td>Here you can <a href="broken://pages/cb1cd8d93c2e69c36d452959a75a8ec501af8f4b#schritt-2-dem-asset-template-charakteristiken-hinzufugen">↗ asset characteristics</a> change and refine the values individually.</td></tr><tr><td><strong>[V]</strong></td><td>Save</td><td>Click to save</td></tr></tbody></table>


---

# 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/english-v14/documentation/assets/ein-asset-konfigurieren.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.
