> 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/activities.md). # Activities Activities can be associated with specific assets, shifts, and calendars, and can include a wide range of different actions and operations, such as maintenance tasks, quality checks, or other types of production-related activities. Each activity in TilliT is associated with a specific set of instructions or procedures that need to be followed in order to complete the task successfully. These instructions can include information on the tools or equipment that are required, the specific steps that need to be taken, and any safety precautions or other considerations that need to be taken into account. ### Listing activities 1. Collect all the setup procedures, quality checks, inspections, paper forms, etc. involved in running the production process. Determine which of these operations will be digitalized in TilliT. 2. Review all parameters, attributes, and variables used or produced in the manufacturing process to uncover data configurations and relationships. 3. Record the frequency and timing of quality checks, as well as the operators who perform them. This information serves as the foundation for developing an Activity Template. --- # 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/activities.md?ask=&goal= ``` `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.