# Asset Modeling

After defining the **Data Fields** from your Asset, the next step is to decide how those fields should be structured into **Asset Tags**.

Asset Tags are the core data elements used by other Core Tags, Workflows, and Applications. They can:

* Reference one or more Data Fields
* Be renamed or grouped
* Apply calculations or transformations
* Align with a specific data model

EasyEdge gives you full flexibility through three distinct **Asset Modeling** methods — each designed for different needs.

<figure><img src="/files/2nv1I0EVzWpGqM3joDPr" alt=""><figcaption></figcaption></figure>

#### Available Methods

**🚫 Do Not Process Data Fields**

No Tags will be generated automatically. You’ll manually create each Tag and define its logic using expressions that combine one or more Data Fields.

**Best for:**

* Advanced engineering scenarios
* Custom mappings or calculations
* Full control over tag creation

**🔁 1-to-1 Mapping**

Automatically creates one Tag per Data Field, with a direct binding. Tag names are based on the Data Field but can be edited later.

**Best for:**

* Fast modeling
* When Data Fields already match the required structure
* Projects where minimal changes are needed

**🤖 AI Modeling**

Uses the EasyEdge AI Copilot to analyze your Data Fields and automatically generate a set of Tags that follow a selected **Data Model** from your Library.

**Best for:**

* Standardizing projects across multiple sites
* Reducing manual effort
* Ensuring consistent tag structures aligned with predefined models


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://easyedge.gitbook.io/easyedge/connect-to-assets/asset-modeling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.