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

# Asset details

The Asset Details window gives you access to many functions of an individual asset

## Overview

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/FwmzBV0eNlQQ7gIFrKOp/Charakteristics.png" alt=""><figcaption><p>Fig. 1 – The Asset Details, tab "General"</p></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="95.33333333333331"></th><th width="182"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/ein-asset-konfigurieren.md">-> Information</a></td><td>In this section, you can configure the selected asset</td></tr><tr><td><strong>[B]</strong></td><td>Attributes</td><td><p>Displays the attributes of the asset.</p><p>You can learn more about attributes in the chapter <a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/asset-modellierung-templates-erstellen.md">-> Asset modeling</a></p></td></tr><tr><td><strong>[C]</strong></td><td>Tabs with quick access</td><td><p>Quick access to information and settings belonging to the respective asset</p><ul><li>General</li><li>Data</li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen.md">-> Alerts</a></li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/tickets.md">-> Tickets</a></li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regeln.md">-> Rules</a></li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/digitaler-zwilling.md">-> Digital Twins</a></li></ul></td></tr><tr><td><strong>[D]</strong></td><td>QR code</td><td>A <a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/qr-codes-generieren.md">-> QR code</a> generate</td></tr><tr><td><strong>[E]</strong></td><td>Go to...</td><td><p>Quick access to</p><ul><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/karte-und-stockwerk.md">-> map and floor</a></li><li>-> data</li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/tickets.md">-> create ticket</a></li><li><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/analytics-and-reports.md">-> Analytics</a></li></ul></td></tr><tr><td><strong>[F]</strong></td><td>Attachments</td><td>Using these, you can <a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/dokumente-an-assets-anhangen.md">-> attach documents</a></td></tr><tr><td><strong>[G]</strong></td><td>Links</td><td>Using these, you can <a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/einem-asset-links-hinzufugen.md">-> add links</a></td></tr><tr><td><strong>[H]</strong></td><td>Ratings</td><td>Here you can<a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/bewertungen.md"> -> ratings</a> be viewed and created for the asset.</td></tr></tbody></table>

## Open asset details

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/rEiXjaL7F4uRaAFl4AwB/F50B2A4C-63FC-47F0-946C-1E254889BFEA.png" alt=""><figcaption><p>Fig. 2 – The asset menu with the asset list</p></figcaption></figure></div>

1. Click in the menu bar on **Assets \[A]**\
   ▷ The "Assets" menu with the **asset list \[C]** appears
2. Click the name of the asset you want to configure **\[B]**\
   ▷ The [-> "Asset Details"](https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/asset-details.md) open (Fig. 1)

## Search and filter attribute values

The redesigned values box in the tab **General** provides clarity even with many attributes. By default, it only shows enabled attributes with a value.

Use the search bar and filters to narrow down the displayed attributes:

* **Search attributes:** Search for the displayed attribute name.
* **Category:** Filter by an attribute category, for example inputs or outputs.
* **Type:** Filter by the attribute type.

The figure shows the English-language interface under **Assets** **\[A]**.

<div data-full-width="true"><figure><img src="https://156899794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNyvwhz1kEMXcHf4HLuZ8%2Fuploads%2Fgit-blob-86ba08934c83c8071176b8caf0dcf96865175d5b%2Fv14-unconnected-attributes-visible.png?alt=media" alt="Wertebox mit Suchleiste, Kategorie- und Typfilter sowie zusätzlich eingeblendeten Attributen ohne Werte"><figcaption><p>Fig. 3 – The revised values box with search and filters; additional attributes are shown</p></figcaption></figure></div>

With **Show unconnected** (**Show unconnected**) **\[B]** if needed, also show deactivated attributes or attributes without a value. These appear faded in the group **Unconnected** (**Not connected**) **\[C]**. Search and filters also apply to this group. The label does not necessarily mean that a data point assignment is missing.

If an expected attribute is missing, delete the search text, set **Category** and **Type** to **All** and activate if necessary **Show unconnected**. Showing and hiding only changes the display, not the attributes or their data connections.


---

# 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/asset-details.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.
