> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/planning/data-gathering/assets.md).

# Site & Assets

### Listing assets

To get started with organising assets in TilliT, begin by creating a comprehensive list of all assets on the site, including areas or lines and machines. The TilliT asset hierarchy is structured as Site -> (Line or Area) -> Equipment.

### Classifying assets

Next, group assets into classes to simplify activity assignments. For example, you might group Line 01 and Line 02 into a "Lines" class. This will help define rules that are common to all the equipment belonging to the same class. You can only have one class assigned to an asset.

Additionally, you can use tolerances to define operational limits during an activity and add guidance and quality checks

### Examples

{% tabs %}
{% tab title="General" %}

```
Site: Melbourne
└── Packing
    ├── Line 1
    │   ├── Machine 1
    │   └── Machine 2
    └── Line 2
        ├── Machine 3
        └── Machine 4
```

{% endtab %}

{% tab title="Wine" %}

```
Line 1
├── Depalatizer
├── Filler/Capper
├── Labeller
├── Packer
└── Palletizer
```

{% endtab %}

{% tab title="Inject Moulding" %}

```
Site: Dallas Site
└── Manufacturing
    ├── MX200
    ├── MX300
    └── MX400
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.tillit.cloud/tillit/planning/data-gathering/assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.