---
title: Asset Types
id: "en:tracking:admin:assettypes.adoc"
site: en
component: tracking
module: admin
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/tracking/3.0/admin/assettypes.html"
source_repo: "https://github.com/iot-invent/xCloud.git@3.0.x"
source_path: tracking/docs/en/modules/admin/pages/assettypes.adoc
---

# Asset Types

In this area, the user has the option to create, edit, or delete asset types.

![Assettypes](_images/tracking_app_admin_assettypes.png)

## Reference

| Module | Description |
| --- | --- |
| ![refresh](_images/refresh.svg) Refresh | Refreshes the asset types list |
| ![plus](_images/plus.svg) Plus | Create asset type |
| ![edit](_images/edit.svg) Edit | Edit asset type |
| ![delete](_images/delete.svg) Delete | Delete asset type |
| ![delete](_images/info.svg) Info | Number of displayed asset types |
| ![assetList](_images/tracking_app_admin_assettypeslist.png) | Asset types list |

## Asset Type List

This list displays all asset types within a space along with general information’s.

![assetList](_images/tracking_app_admin_assettypeslist.png)

### Attributes

| Field | Type | Description |
| --- | --- | --- |
| Type ID | Text | ID of the asset type |
| Name | Text | Name of the asset type |
| Category | DropDown | Category of the asset type |
| Routes | Counter | Number of routes |

## Automatic Asset Assignment

When a tag reports in that is not assigned to any asset yet, the asset can be created automatically. One or more rules can be configured per asset type for this — in the asset type’s edit dialog, on the **Automatic asset assignment** tab.

Without a matching, enabled rule nothing happens: in a space where no asset type carries such a rule, no assets are created automatically, no matter how many positions arrive there.

> **NOTE:** The tag has to be known in the tag administration. A tag the locating hardware has never reported cannot be assigned.

### Attributes

| Field | Type | Description |
| --- | --- | --- |
| Enabled | Toggle | Only enabled rules are evaluated |
| Tag property | DropDown | Which property of the tag is evaluated: **Id** (the technical identifier, for example the MAC address) or **Name** (the readable name from the tag administration) |
| Tag prefix | Text | Mandatory. Only tags whose value starts with it are covered by this rule. A trailing `*` is customary but not required |
| Asset name mode | DropDown | How the asset name is derived from the value |
| Separator | Text | Only visible for **Part before the separator** and **Part after the separator**, and mandatory there. The characters `= < > \ { }` are not allowed |

### Example

Tag name `27B330061706540953+00005`, tag prefix `27B330061706540953*`, separator `+`:

| Asset name mode | Result |
| --- | --- |
| Part after the separator | `00005` |
| Part before the separator | `27B330061706540953` |
| Full tag property | `27B330061706540953+00005` |

> **IMPORTANT:** The separator is looked for from the start of the whole value, inside the prefix as well. For the MAC address 10:3D:1C:9E:4C:C4 with : as the separator, Part before the separator therefore yields 10 and not 10:3D:1C. Upper and lower case are distinguished.

### How the assignment works

For every incoming position of a tag, in this order:

1.  If the tag is already assigned to an asset, that asset is used. The rules are not evaluated at all.

2.  Otherwise **exactly one** enabled rule across all asset types of the space has to match.

3.  The asset name is derived from the tag.

4.  If an asset of this asset type with this name already exists in the space, the tag is added to it. **No second asset is created.**

5.  Only otherwise is a new asset created with this name and this asset type.

In addition:

-   The asset name is unique per asset type. The same name under a different asset type is a separate asset.

-   A tag is always assigned to at most one asset.

-   An incomplete rule — without a tag prefix, without a tag property or without an asset name mode — has no effect.

-   If the value yields no name, for instance because the separator is at the end, no asset is created.

> **NOTE:** Two rules that could claim the same tag cannot be saved. This is checked when the rule is entered and when the asset type is saved, across all asset types of the space in both cases. Rules overlap when they read the same tag property and one prefix starts with the other — 27B3* and 27B330061706540953* both cover the same tag, for instance. The separator plays no part in it, because a tag value can contain both.

> **NOTE:** If you work with application spaces (see Space type), the same tag becomes a separate asset in every application space. That is intended — every use case keeps its own inventory.