> For the complete documentation index, see [llms.txt](https://40factory.gitbook.io/wilson/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://40factory.gitbook.io/wilson/3.11/best-practices/identifying-the-use-case-preliminary-checks-and-guidelines.md).

# Identifying the Use Case: Preliminary Checks and Guidelines

## Test Preparation: Key Elements for Defining the Use Case

It is essential to establish:

### 1. Use Case

Determine the type of questions the system should answer. Focus on the value it can bring, the company’s needs, and concrete examples within the organization.

{% hint style="info" %}
We recommend starting with a single use case to simplify documentation collection and testing activities. For example, it is useful to begin with documentation related to a single machine model to validate the bot configuration and the knowledge base before extending the system to the entire installed base.
{% endhint %}

### 2. Document Sources

Identify the company information used to answer these questions.

### 3. Categorization

Understand how this information is organized to define the context (e.g., manuals organized by model, serial number, machine group, etc.).

## Initial Settings: First Steps for Interaction

1. Review descriptions of documents and images and add tags (Knowledge Base).
2. Define bots with specific prompts based on the operational context (Settings > Bot Management > Edit) and associate them with folders (Settings > Bot Management > Edit Filter).
3. Enable users (Settings > Admin Users > Edit User > bot selection).


---

# 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://40factory.gitbook.io/wilson/3.11/best-practices/identifying-the-use-case-preliminary-checks-and-guidelines.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.