> 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/configure-attributes.md).

# Add and Configure Attributes

Add attributes to an asset template to define its datapoints, such as power measurements or operating states. Use the attribute editor to configure their units, historical recording, translated titles, analytics defaults, Augmented Reality (AR) position, and displayed value text.

All five tabs belong to the same attribute configuration:

* [General](#general)
* [Conversions](#conversions)
* [Title language](#title-language)
* [Pipeline & AR](#pipeline-and-ar)
* [Value mapping](#value-mapping)

## Prerequisites

* You have write access to **Asset Modeling**.
* You have [created an asset template](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/asset-core/create-a-new-template.md#step-1-create-the-template) that you can edit.
* For conversions, configure the attribute's **Class** and **Default unit** in [General](#general) first.
* For historical analysis, enable **Trending mode** in [General](#general).

## Open or Add an Attribute

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-16c9260f82657ebeb21579e1221803033865f651%2Fattribute-settings-open.png?alt=media" alt="Current Asset Core template details with Platform Core navigation and the Template button beside Attribute templates marked"><figcaption><p>Open a template attribute or add one from the Attribute templates list.</p></figcaption></figure>

1. Open **Platform Core** **\[A]**.
2. Select **Asset Core**.
3. Open the asset template.
4. Select **Template** **\[B]** beside **Attribute templates**.\
   ▷ The attribute editor opens on **General**.

To configure an existing attribute instead, select its name under **Attribute templates**.

{% hint style="info" %}
Switching tabs keeps your unsaved changes in the form; it does not save them. Select **Save** to apply attribute settings. If you select **Back** with unsaved changes, choose **Keep Edit** to continue or **Leave Without Saving** to discard them. Custom conversion changes have a separate save process, described under [Conversions](#conversions).
{% endhint %}

## General

Use **General** to define the datapoint and how its values are handled. The figure shows an existing analog power attribute with the **power** class, **kW** as its default unit, and historical recording enabled.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-c8d29cf759eaa2153899bf774ee697d206155926%2Fattribute-settings-general.png?alt=media" alt="General tab with the value type, attribute name, class, default unit, trending control, and Save marked"><figcaption><p>General settings for an existing template attribute.</p></figcaption></figure>

| Reference | Setting                                      | Purpose                                                                                                                                                                                                                                                                                         |
| --------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **\[A]**  | **Platform Core**                            | Navigation to Asset Core and its asset templates.                                                                                                                                                                                                                                               |
| **\[B]**  | **Asset value type**                         | Select **Analog** for numerical measurements, such as power, or **Digital** for two-state signals, such as 0 and 1.                                                                                                                                                                             |
|           | **Virtual**                                  | Enable a datapoint calculated from other attributes. Enter a **Default calculation** before saving a virtual attribute.                                                                                                                                                                         |
| **\[C]**  | **Attribute**                                | Enter the technical attribute name when creating it. The name is required and cannot contain `.`, `{`, `}`, `[`, or `]`.                                                                                                                                                                        |
|           | **Subtype**                                  | Select **Input** for incoming data, **Output** for outgoing commands, **Status** for state information, or **Information** for descriptive data.                                                                                                                                                |
| **\[D]**  | **Class**                                    | Classify the attribute, for example as **power**. The class determines available units and affects which functions are available.                                                                                                                                                               |
| **\[E]**  | **Default unit**                             | Select the unit of the attribute's values, for example **kW**. The choices depend on **Class**. Changing the class clears the selected unit, so select the unit again.                                                                                                                          |
|           | **Default calculation**                      | Enter an expression to scale, convert, or calculate values. See [The Calculator](https://docs.buildings.ability.abb/collection/mandatory-base/assets/attribute-functions/calculate-values-the-calculator.md) for syntax and examples. **Reset by default** restores this field's initial value. |
| **\[F]**  | **Trending mode**                            | Enable historical recording when you need trends or historical analytics. Select **On change** to store changed values or **Always** to store every value, including repeated values.                                                                                                           |
|           | **Limit low**, **Limit high**, **Step size** | Enter optional lower-limit, upper-limit, and increment settings. For example, 0, 1000, and 10 describe a range from 0 to 1000 with increments of 10.                                                                                                                                            |
| **\[G]**  | **Save**                                     | Apply the attribute settings.                                                                                                                                                                                                                                                                   |

{% hint style="info" %}
**Attribute** and **Subtype** are set when you create the attribute and are read-only when you reopen it. Use [Title language](#title-language) to provide translated display titles.
{% endhint %}

To add an attribute:

1. Select **General**.
2. Select the **Asset value type** **\[B]**.
3. Enter the **Attribute** name **\[C]**.
4. Select its **Subtype**.
5. If applicable, select a **Class** **\[D]**.
6. If applicable, select its **Default unit** **\[E]**.
7. Select **Save** **\[G]**.\
   ▷ The new attribute appears under the template's **Attribute templates**.

Open the saved attribute again to configure the other tabs. When you save changes to an existing attribute, the editor stays open.

## Conversions

Use **Conversions** to display values in another unit, as a cost, or as an emissions equivalent in [Insight Analytics](https://docs.buildings.ability.abb/collection/platform/insight-analytics/apply-unit-cost-and-emissions-conversions.md). The attribute's **Default unit** is the source unit. For example, a kWh-to-MWh conversion displays `1000 kWh` as `1 MWh` without changing the recorded readings.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-34153b256aba04b2b73147db39fbf778dc46b350%2Funit-conversions-list.png?alt=media" alt="Conversions tab for an energy attribute with preconfigured unit conversions and custom cost and emissions ranges"><figcaption><p>Conversion list and controls for a kWh attribute.</p></figcaption></figure>

| Reference | Element                      | Meaning                                                                                                                                          |
| --------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **\[A]**  | **Conversions**              | Open the conversions for this attribute's source unit, grouped under **Unit conversions**, **Cost**, and **Emissions**.                          |
| **\[B]**  | **Default unit**             | Check the source unit. Configure and save it in [General](#general) first.                                                                       |
| **\[C]**  | Preconfigured conversion     | Inspect its **Unit**, **Active** dates, and **Formula**. The example converts kWh to MWh using `x × 0.001`.                                      |
| **\[D]**  | Custom cost range            | Apply a rate to express values in a currency. The EUR example uses a factor of `0.18` per kWh.                                                   |
| **\[E]**  | **Create custom conversion** | Open the dialog to add a conversion or another validity range.                                                                                   |
| **\[F]**  | Pencil icon                  | Open a custom range for editing, change its settings in the dialog, then select **Save**.                                                        |
| **\[G]**  | Delete icon                  | Delete the custom range immediately, without confirmation. Deleting its last range also removes the custom conversion.                           |
| **\[H]**  | Custom emissions range       | Apply a factor to express values in the configured emissions unit. Use an appropriate destination unit and approved factor for your calculation. |

{% hint style="warning" %}
Custom conversions are shared within your tenant for the same source unit. Changing **Unit** or **Purpose** affects all ranges of that conversion; changing dates, **Factor**, or **Offset** affects the selected range. Conversion changes save separately from the attribute form, so leaving the attribute editor without saving does not undo them.
{% endhint %}

### Custom Conversion Settings

1. Select **Create custom conversion** **\[E]** in the conversion list.\
   ▷ The **Custom conversion** dialog opens.
2. Enter the conversion settings using the field reference below.
3. Select **Save** **\[G]** in the dialog.\
   ▷ The saved range appears in the corresponding conversion group.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-5dfb21a9306616f53a3612242496687c71b1f0c8%2Funit-conversions-create.png?alt=media" alt="Custom conversion dialog with Unit, Purpose, validity dates, Factor, Offset, Save, and Cancel marked"><figcaption><p>The same fields configure a new conversion or an existing custom range.</p></figcaption></figure>

| Reference | Dialog field or control | What to enter or do                                                                                                                  |
| --------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **\[A]**  | **Unit**                | Select the destination unit, such as MWh, a currency for cost, or an appropriate emissions unit.                                     |
| **\[B]**  | **Purpose**             | Select **Unit conversion**, **Cost**, or **Emission** to determine where the conversion is offered in Analytics.                     |
| **\[C]**  | **Active from**         | Enter the first date on which the range applies.                                                                                     |
| **\[D]**  | **Active to**           | Enter the last date on which it applies, on or after **Active from**. Both endpoints are included.                                   |
| **\[E]**  | **Factor**              | Enter the positive multiplier for the source value. For a cost conversion, enter the rate per source unit. The initial value is `1`. |
| **\[F]**  | **Offset**              | Enter the constant added after multiplication; leave `0` when no offset is needed.                                                   |
| **\[G]**  | **Save**                | Save the conversion directly; the attribute page's separate **Save** is not required.                                                |
| **\[H]**  | **Cancel**              | Close the dialog without saving its changes.                                                                                         |

The calculation is `result = value * factor + offset`. For example, a factor of `0.18` and offset of `0` convert `1000 kWh` to `180 EUR`. The figures show demonstration settings, not recommended tariffs or emissions factors.

To add a later rate, use **Create custom conversion** again with the same **Unit** and **Purpose** and a new, non-overlapping date range. For consecutive periods, end one on 31 December and start the next on 1 January. If dates overlap an existing range, adjust them or edit that range instead.

{% hint style="warning" %}
Cover the entire period you want to analyze. Values outside an active range remain numerically unchanged, which can produce misleading results. After configuring a conversion, [apply it in Insight Analytics](https://docs.buildings.ability.abb/collection/platform/insight-analytics/apply-unit-cost-and-emissions-conversions.md) and check the output unit and analysis period.
{% endhint %}

## Title language

Use **Title language** to provide display titles in different interface languages without changing the technical **Attribute** name. For example, the same power attribute can have the English title **Power** and the German title **Leistung**.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-06ca56574d0cb1ab28fbae8eb590e9a4661c425e%2Fattribute-settings-title-language.png?alt=media" alt="Title language tab with Translation, an English title, a translation&#x27;s delete icon, and Save marked"><figcaption><p>Translated titles for one template attribute.</p></figcaption></figure>

1. Select **Title language**.
2. Select **Translation** **\[A]**.\
   ▷ A language selector and title field are added under **Title language and text**.
3. Select the language for the row.
4. Enter its translated title **\[B]**.
5. Repeat steps 2-4 for each additional language.
6. Select **Save** **\[D]**.\
   ▷ The translated titles are saved on the attribute.

To remove a title, select the row's delete icon **\[C]**, then select **Save** **\[D]**. Each language can be selected once.

## Pipeline & AR <a href="#pipeline-and-ar" id="pipeline-and-ar"></a>

Use **Pipeline & AR** to set preferred analytics aggregation settings and choose the attribute's position in the Augmented Reality display.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-f579ffca1165b24d9d3323706437712839cd648d%2Fattribute-settings-pipeline-ar.png?alt=media" alt="Pipeline and AR tab with Mode, Function, Interval, AR Position, and Save marked"><figcaption><p>Preferred analytics aggregation and Augmented Reality position.</p></figcaption></figure>

### Aggregation Defaults

**Pipeline raster** provides preferred settings for new Insight Analytics datapoint series. For example, use an hourly average for a temperature measurement instead of selecting the same aggregation each time you add it to an analytic.

| Reference | Setting                    | When to use it                                                                                                                                                         |
| --------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **\[A]**  | **Mode: None**             | Leave the preferred mode unspecified for new analytics series.                                                                                                         |
| **\[A]**  | **Mode: Current value**    | Start new series with recorded values rather than aggregated values.                                                                                                   |
| **\[A]**  | **Mode: Aggregated value** | Start new series with values calculated over a defined interval. **Function** and **Interval** become available.                                                       |
| **\[B]**  | **Function**               | Choose an aggregation appropriate to the measurement. For example, **Average** summarizes temperature over each interval.                                              |
| **\[C]**  | **Interval**               | Choose the time window for each aggregated value. For example, **H1** represents one hour. Shorter intervals retain more detail; longer intervals give a coarser view. |

1. Select **Pipeline & AR**.
2. Select a **Mode** **\[A]** under **Pipeline raster**.
3. If you select **Aggregated value**, select a **Function** **\[B]**.
4. If you select **Aggregated value**, select an **Interval** **\[C]**.
5. Select **Save** **\[E]**.\
   ▷ The preferred aggregation settings are saved on the template attribute.

When you add a new datapoint series to an analytic, Insight Analytics reads these preferences. Updating template defaults leaves settings already configured on existing series unchanged.

You can override **Mode**, **Function**, and **Interval** for an individual series in the [Summary Table](https://docs.buildings.ability.abb/collection/platform/insight-analytics/the-insight-analytics-interface/summary-table.md#aggregation-settings-for-a-series). This changes the analytic's series settings, not the template defaults. See [Aggregations](https://docs.buildings.ability.abb/collection/academy/aggregations-in-eliona.md) for the aggregation functions.

{% hint style="info" %}
Configure historical recording separately under **Trending mode** in [General](#general). Aggregation defaults do not replace the trending configuration.
{% endhint %}

### AR Position

Use **Select position** **\[D]** under **AR Position** to choose where the attribute appears in the Augmented Reality display.

| Option           | Use                                                  |
| ---------------- | ---------------------------------------------------- |
| **No Position**  | Leave the attribute without an assigned AR position. |
| **Top**          | Show the attribute at the top.                       |
| **Bottom Left**  | Show the attribute at the bottom left.               |
| **Bottom Right** | Show the attribute at the bottom right.              |

1. Select the position **\[D]**.
2. Select **Save** **\[E]**.\
   ▷ The AR position is saved on the attribute.

## Value mapping

Use **Value mapping** to display readable text for numerical values or ranges. For example, show **Idle** or **Running** instead of a raw number.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-ba3be788ff73263f1576c9d2fdcea6ce69ee76d4%2Fattribute-settings-value-mapping.png?alt=media" alt="Value mapping tab with Mapping, the numeric upper limit, result text, delete icon, and Save marked"><figcaption><p>Value mappings with upper limits of 0 and 1000.</p></figcaption></figure>

Each numeric entry is an **inclusive upper limit**. The displayed text comes from the smallest configured limit greater than or equal to the actual value.

| Enter value | Enter result | Displayed range in this example                       |
| ----------- | ------------ | ----------------------------------------------------- |
| `0`         | `Idle`       | Values less than or equal to 0.                       |
| `1000`      | `Running`    | Values greater than 0 and less than or equal to 1000. |

For these settings, both `750` and `1000` display **Running**. A value above `1000` is displayed numerically because it exceeds the highest configured limit. Mapping controls displayed text; use [Conversions](#conversions) to convert units.

1. Select **Value mapping**.
2. Select **Mapping** **\[A]**.\
   ▷ A row with **Enter value** and **Enter result** is added.
3. Enter the numeric upper limit **\[B]**.
4. Enter the text to display **\[C]**.
5. Repeat steps 2-4 for each additional range.
6. Select **Save** **\[E]**.\
   ▷ The value mappings are saved on the attribute.

To remove a range, select its delete icon **\[D]**, then select **Save** **\[E]**.

## Next Steps

* Continue [adding characteristics to the asset template](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/asset-core/configure-a-template.md#add-characteristics).
* [Create assets](https://docs.buildings.ability.abb/collection/mandatory-base/assets/create-assets.md) that use the template.
* Use the datapoints in [Insight Analytics](https://docs.buildings.ability.abb/collection/platform/insight-analytics.md).


---

# 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/configure-attributes.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.
