---
title: Asset Metadata
slug: concepts/asset-metadata
docTags: 5eNNX_Hobhvyt7KEHa8S7,9n2wuycJLU1kOZ3C8Gkr-
createdAt: 2025-08-13T08:13:30.977Z
---

## What is Asset Metadata?

**Asset metadata** is static information that defines context or descriptive attributes of [Assets](docId\:C4opdlUcIrJ0DRaeXrIsp).

:::hint{type="info"}
The term **Metadata** is also used in [Asset Properties](docId\:Cr6HbrDSl8FsuVlVm20IF) and [Measurements](docId\:XQWLEmDcNfff3-0H-GMmS). It refers to the static nature of the information that is stored this way.
:::

It allows you to say:

- “This asset is located in Hall B, Packaging Area.”
- “The maximum rated capacity of this mixer is 500 kg.”

In other words, asset metadata is the set of descriptive fields that give some additional background to an asset, independent of live or historical measurements.

## Why does it matter?

There is plenty of relevant information that does not come from a PLC or a sensor, but instead derives from the specification of a machine, the physical environment it is located in, or the mind of an operator. **Asset metadata** can be used to capture this information and use it effectively alongside time-series data.

So in the end you can enrich your dataset with relevant business and engineering information.

## How does it fit in the system?

Each asset, regardless of its position in the asset tree, can have a set of **metadata fields**. These fields consist of a name and a value.

The values you assign to metadata fields can be used in [Calculations](docId\:OpIoDkGNNgYjeDX6zkg_D), e.g. to calculate the tank volume based on a level measurement and the diameter specification of the tank.

In [Asset Prototypes](docId\:B7RjC9mYVP_lIc5wBr_yW), you can use asset metadata fields to determine the measurement names that should be linked to newly instantiated asset properties.

## Example

For a **Mixer** asset, metadata could include:

- Location → Hall B
- Capacity → 500 kg
- Manufacturer → ACME Corp
- InstallationDate → 2022-03-14

## When you use it

You’ll work with asset metadata when:

- You want to store static information about your [Assets](docId\:C4opdlUcIrJ0DRaeXrIsp)
- Configuring [Calculations](docId\:OpIoDkGNNgYjeDX6zkg_D) that depend on certain attributes (e.g. engineering specifications) of an asset
- Building [Asset Prototypes](docId\:B7RjC9mYVP_lIc5wBr_yW) that can automatically link the correct measurements to the newly created asset properties.

## Common misconceptions

- **Asset metadata is not live data.** It doesn’t point to time series measurements or calculations. That’s the role of [Asset Properties](docId\:Cr6HbrDSl8FsuVlVm20IF).
- **It is not automatically generated.** It must be defined explicitly for each asset.

## Best practices

- Define a standard set of metadata fields per asset prototype (e.g., Location, Engineering limit, Manufacturer).

:::hint{type="info"}
When configuring asset properties on [Asset Prototypes](docId\:B7RjC9mYVP_lIc5wBr_yW), keep in mind that they are **required fields** when instantiating a new asset from a prototype.
:::

- Keep asset metadata concise but meaningful. Avoid cluttering assets with unnecessary attributes.
- Avoid storing information that frequently changes in asset metadata. This decreases the maintainability of your dataset.

## More information

- Standardizing Metadata with [Asset Prototypes](docId\:B7RjC9mYVP_lIc5wBr_yW)
- [Using metadata to reuse calculations](docId\:VmElwzGf3OvtOToKgJ61Q)