---
title: Configure
slug: uns/configure
docTags: 
createdAt: 2025-01-23T21:16:27.308Z
---

Use the **Configure **Unified Namespace (UNS) page to define and manage the hierarchical structure of your UNS. This allows you to organize your enterprise's data and assets into a standardized hierarchical format.

On the *Configure* page, you can:

- Define the overall structure of your UNS using a simple string.
- Add rules to classify incoming data for the first three levels of the hierarchy.

# UNS Hierarchy Configuration

The UNS Hierarchy represents your enterprise as a hierarchy of classes, such as **Enterprise**, **Site**, **Area**, and **Production Unit.** Each level in this hierarchy reflects your physical or data structure, helping to standardize and unify how data flows across the organization. 

For example:

:::BlockQuote
enterprise/site/area/production\_unit
:::

This hierarchy:

- Decouples how data is gathered and consumed.
- Lets users access unified data without needing to understand sensor or device-level details.

# Configure your UNS Hierarchy

Before setting up your UNS hierarchy, take time to plan your class structure and hierarchy levels. The class structure is the foundation of your UNS setup and should be validated before you begin.

If you modify the class structure or hierarchy levels after the initial setup, you must delete the existing connector and create a new one. This ensures the updated structure is correctly reflected across all Litmus Edge components.

:::hint{type="info"}
**Note**: Before configuring your UNS, also consider the following:

- Changes to rules immediately updates how data is organized. Changes to the structure resets the rules and data is not longer unified.
- Each class name and rule must use letters, numbers, or symbols(**`-`,** **`_`**).
- The UNS structure string cannot exceed** 256** characters.
- You cannot apply rules to the fourth level (**Production Unit**) in the current version.
:::

**To configure UNS:**

1. Navigate to **Unified Namespace (UNS) **> **Configure **page.
   The *Configure UNS* tab opens.

   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Jo8oFjoX1NRDoB_AoCc3T_image.png" size="80" width="1276" height="531" position="flex-start" caption="Configure UNS tab" showCaption="true"}
2. Refer to the following configurations:
   - **UNS Structure: **Enter your UNS structure. For example: `enterprise/site/area/production_unit`
     - Use a forward slash `/` to separate the levels of your hierarchy.
     - Click **Save UNS**.
   - **Class configurations: **Define **Class Rules **for the first three levels:
     - **Enterprise**: Add one rule to classify this level.
     - **Site**: Add up to 10 rules, such as country names (e.g., Australia, Brazil).
     - **Area**: Add up to 10 rules for finer classification (e.g., manufacturing zones).
   - Click **Save rules** to apply the structure and rules.

     ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Kf1zBS6zR9lHQRpJg2t_s_image.png" size="74" width="663" height="874" position="flex-start" caption="Configure UNS tab" showCaption="true"}

# Rules Overview 

Class rules help match and organize incoming topics as part of your UNS. For example, if your Site rules include *Australia*, any data tagged with `Australia` will be categorized under that Site.

### Managing Class Rules

- To add a rule, click **Add new rule** under the relevant class.
- To delete a rule, click the **red trash **icon next to it.
- Save your changes by clicking **Save rules**.

  ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/RCbI37SR96hsDAaWGuGKn_image.png" size="60" width="513" height="742" position="flex-start" caption="Class configurations pane" showCaption="true"}