> 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/mandatory-base/assets/asset-modeling-create-templates.md).

# Asset Modeling: Create Templates

## Asset Modeling

**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](/collection/mandatory-base/assets/create-assets.md), 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**.

An attribute's default unit also determines its available [unit, cost, and emissions conversions](/collection/mandatory-base/assets/asset-modeling-create-templates/conversions.md). Open its **Conversions** tab to inspect preconfigured conversions or manage shared custom ranges.

### **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
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/mandatory-base/assets/asset-modeling-create-templates.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.