# Asset Modeling

{% hint style="info" %}
All information on the topic of assets can be found in the chapter [↗ Asset Modeling](https://docs.buildings.ability.abb/collection/mandatory-base/assets/asset-modeling-create-templates)
{% endhint %}

**Asset templates** are a kind of **"blueprint"** for assets. They determine which **attributes** an asset has, such as **"temperature," "humidity," "light intensity," or the "number of people."** These attributes define the values that can be monitored or controlled with an asset.

When you [↗ create a new asset](https://docs.buildings.ability.abb/collection/mandatory-base/assets/create-assets), you will be prompted to select an **asset template**. The asset created this way will then contain all the **predefined attributes** of the template.

## **Why Use Asset Templates?**

Manually creating assets can be very time-consuming, especially if each asset needs to be equipped with specific attributes.

With **asset modeling**, you can **create templates for different asset types** and **reuse them as often as you like**.

### **Example: Smoke Detector**

A building contains **hundreds of smoke detectors**.

* **Without asset modeling**, you would have to create each smoke detector individually and equip it with the appropriate attributes.
* **With asset modeling**, you create the "Smoke Detector" asset template once. This template already contains all the relevant attributes. When you now create a new smoke detector, you simply duplicate the template and only adjust the **specific properties** such as location or ID.

▷ *This saves time and ensures uniform management of your assets.* 🚀


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.buildings.ability.abb/collection/getting-started/2.-setting-up-assets/asset-modeling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.