> 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/knowledge-base/oee/a-step-to-quality.md).

# A Step to Quality

## Getting Reject Counts

You will need to complete the **performance** steps prior to start measuring quality, as this is the measure of good products minus rejected products. For this part, the important part is getting the data about **reject counts** into TilliT. This is to assess how much are you passing or failing your products.

For best results, you need to read local data sources with a TilliT Edge device or Integrate via API/MQTT.

However, this can also be added via an operator completing an Activity (see [Activity Templates](/tillit/knowledge-base/setting-up-tillit/activity-templates.md), be sure to choose "Order Reject" as the item type).

<figure><img src="/files/5LSr3WOyFajS2QW2IEcD" alt="" width="284"><figcaption></figcaption></figure>


---

# 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/knowledge-base/oee/a-step-to-quality.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.