> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/oee/sites.md).

# Sites

Emulate the real world with Site / Area / Equipment structure and per-Site configuration (location, time zone, shifts, products).

The **Sites** page (`OEE → Sites`) is where you build and maintain the OEE site structure. The left-hand pane is a tree of every Site, Area, and Equipment in your installation; the right-hand pane is a tabbed editor whose contents change depending on which node is selected.

<figure><img src="https://570593659-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMGRODsc2QD3N3wmfwTl%2Fuploads%2Fgit-blob-22cb66391f35baa19c0bd5aabca79d35600c3010%2Foee-site-settings.png?alt=media" alt=""><figcaption><p>OEE Sites — tree on the left, configuration tabs for the selected node on the right</p></figcaption></figure>

***

## What lives here

* **The structure itself** — Sites, Areas under each Site, Equipment under each Area. See [Site Structure](/management-portal/oee/sites/site-structure.md) for how to create and reorganize nodes.
* **Site-level configuration** — three tabs that apply to a Site as a whole:
  * [**Site Settings**](/management-portal/oee/sites/site-settings.md) — name, description, OEE data store, time zone, location on a map.
  * [**Site Shifts**](/management-portal/oee/sites/site-shifts.md) — shift calendars that equipment under this Site can be assigned to.
  * [**Site Products**](/management-portal/oee/sites/site-products.md) — product lists (groups + products + ideal cycle times) used by equipment under this Site.
* **Area configuration** — see [Areas](/management-portal/oee/areas.md). Areas are pure containers and only have a name and description.
* **Equipment configuration** — the seven tabs that turn a piece of equipment into a measured OEE source. Documented under [Equipment](/management-portal/oee/equipment.md).

***

## Working with the tree

The tree view on the left in the OEE area has a few OEE-specific rules:

* **Filter sites** — the search box at the top of the tree filters by Site name. Areas and Equipment are not filtered directly; they appear under any Site that matches.
* **Refresh** — the refresh arrow re-loads the tree from the server, useful when other users have changed the structure.
* **New Site** — opens a dialog to create a Site. With the same inputs contained inside [Site Settings](/management-portal/oee/sites/site-settings.md). It pre-selects the default OEE data store if one exists.
* **Reorder mode** — the lock/arrows toggle next to **New Site** turns on drag-and-drop functionality (reordering). While reorder mode is on, the tree icon shows a lock so you remember to switch it off after reorganizing. See the constraints in [Site Structure](/management-portal/oee/sites/site-structure.md).
* **Right-click / kebab menu** — every node has a kebab (`⋮`) button on hover and a right-click context menu. The menu items depend on the node type:
  * **Site** → Add area / Rename / Delete
  * **Area** → Add Equipment / Rename / Delete
  * **Equipment** → Rename / Delete

<figure><img src="https://570593659-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMGRODsc2QD3N3wmfwTl%2Fuploads%2Fgit-blob-b5accf37e852400ea28f26b38060ff1759857864%2Foee-sites-context-menu.png?alt=media" alt=""><figcaption><p>Sites tree — kebab / right-click context menu on a Site (Add area / Rename / Delete)</p></figcaption></figure>

{% hint style="info" %}
The tree is **disabled while you have unsaved changes** in the right-hand editor — you’ll see a `disabled during editing` tooltip on hover. Save or cancel the open editor to re-enable selection.
{% endhint %}

{% hint style="warning" %}
**You cannot delete a node that has enabled Equipment under it.** Disable OEE on the Equipment first (Equipment tab → **OEE Enabled** off, then Save). Attempting to delete shows an error listing the enabled equipment that’s blocking the operation.
{% endhint %}

***

## Where Sites differ from the rest of Nexus

If you’ve worked with [Asset Hierarchies](/management-portal/designer/assets/asset-hierarchies.md) in Designer, the OEE Sites tree will look familiar — but the two are **independent trees** for two different concerns:

|            | Asset Hierarchies (Designer)                                                | OEE Sites                                                         |
| ---------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Purpose    | Define how data is **collected** from devices (tags, connectors, ingestion) | Define how OEE is **calculated** (state, shifts, stops, products) |
| Node types | Hierarchy → Areas → Assets                                                  | Site → Area → Equipment                                           |
| Time zone  | Per hierarchy version                                                       | Per Site (used for shift evaluation)                              |
| Data store | Per hierarchy                                                               | Per Site (must have the **OEE** purpose)                          |

Most installations end up with one OEE Site per physical plant and a separate Asset Hierarchy that feeds tags into it. The two trees don’t need to mirror each other.