> 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/platform-core/asset-core/create-a-new-asset-characteristic-template.md).

# Create a New Asset Characteristic Template

Asset characteristic templates allow you to define standardized information for assets. These templates contain predefined attributes that are relevant for specific asset types, such as area, capacity, or location. You can use existing characteristic templates or create your own and customize them individually.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FmKWl6MRFRfgscVXRgyqk%2FGroup%2053.png?alt=media&amp;token=55783883-627c-4ee2-bc13-911bfc8c730e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fe7Ahb5m6JYB9hzTWIyZB%2FGroup%2056.png?alt=media&amp;token=5fde6c6c-ea58-4857-9949-0447cf26370b" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FfRKngAjfv03xneHnbZN7%2FGroup%2057.png?alt=media&amp;token=36a9263e-9b28-4724-a748-dab699205c37" alt=""><figcaption></figcaption></figure>

1. Navigate to **Engineering → Asset Modeling**.
2. Open any **Asset Template** by clicking on it.
3. Click on **\[G1]** to open the overview of the available **Asset Characteristic Templates**.\
   ▷ A list of already existing Asset Characteristic Templates opens **\[G3]**.
4. Click on **\[G1]** to open the available **Asset Characteristic Templates**.
5. **Select or create a category**\
   ▷ A list of existing Asset Characteristic Templates opens **\[G3]**.
6. To create a **new category**, click on **\[G4]**.

   <div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FTOHN7mo6AINCHfQ0HwTK%2Fimage%2048.png?alt=media&amp;token=cc126ae1-f469-40a8-ba42-f94f8266af30" alt="" width="208"><figcaption></figcaption></figure></div>

▷ The following window opens to determine the name of the characteristic: 7. To edit an **existing category**, click on **\[G5]**.\
▷ The window **\[G6]** opens. 8. In **\[G7]**, you can manage the **translations** for the selected category. 9. To add a **new attribute**, click on **\[G8]**. 10. The **attribute title** is entered in **\[G9]**. 11. The **unit** of the attribute (e.g., m², persons) is determined in **\[G10]**. 12. To add the **translations for an attribute**:

```
Expand **\[G11]**.
```

13\. In **\[G13]**, you can enter the translation for the respective language. 14. More languages can be added via **\[G12]**. 15. Translations can be removed with **\[G14]**. 16. With **\[G15]**, attributes can be marked to be deleted upon saving. 17. Click on **\[G16]**, to save all changes.

The configured asset characteristics can then be used directly in the asset templates.


---

# 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/platform-core/asset-core/create-a-new-asset-characteristic-template.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.
