> 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/designer/assets/tags/collect.md).

# Collect

A **Tag** defines how a specific datapoint is acquired from connected equipment—it’s the collection contract that states *what* to collect, *from where*, and *how* incoming measurements are handled at the point of ingress. The **Collect** tab contains the Edge-side configuration used to retrieve data and is organized into:

* **General Settings** — Naming and identity (human-readable tag name, the **hierarchical name** derived from ISA-95 Areas/Assets, and the immutable **Cloud Id** for guaranteed uniqueness in the cloud), plus **data direction** (read / write).
* **Configuration** — Data source selection and addressing, including any protocol-specific options.
* **Sampling and Scaling** — Acquisition cadence and value shaping (sampling interval or triggers, and optional linear scaling of measurements).

The figure below shows a screenshot of a tag example configuration.

<figure><img src="/files/PI71StYTi2HUJEMCE3z6" alt=""><figcaption></figcaption></figure>

The following subsections explain how to configure a Tag correctly.