> 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/two-steps-to-performance.md).

# Two Steps to Performance

## Setting default run rates

Define your asset or equipment to have a **default run rate**. This will be your target to achieve 100% performance.

Alternatively, each order can have a different default run rate and order performance will be measured using this instead of the asset or equipment's default run rate.

See [Asset](/tillit/knowledge-base/setting-up-tillit/asset-hierarchy/assets.md)for accessing your assets and changing the Default Run Rate.

## Getting Production Counts

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

See the [Equipment Status Templates](/tillit/knowledge-base/setting-up-tillit/edge/data-tags/data-tag-templates.md) for ingesting via edge or [Publish Order Progress](broken://pages/fcdzpnNQX1AnfVQPfP8x) for using MQTT.

If the equipment does not contain any knowledge about its production count, then use our wireless gateway and sensors offerings to start measuring performance in a matter of hours. Learn more at [Setting up your Site for TilliT Edge](broken://pages/tBDprHEwjSFp4NoL5aVM).

As a last resort, you can ingest production counts for an Activity created inside TilliT for your operators to fill out (see [Activity Templates](/tillit/knowledge-base/setting-up-tillit/activity-templates.md)).


---

# 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/two-steps-to-performance.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.