> 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/configuring-kpi-metrics.md).

# Configuring KPI Metrics

TilliT calculates three types of KPI metrics for assets: **OEE** (Overall Equipment Effectiveness), **OOE** (Overall Operations Effectiveness), and **TEEP** (Total Effective Equipment Performance). Each asset can have up to three KPI configurations, and you can choose which metric appears on the order card.

## Where to configure KPI metrics

KPI metrics are configured in the **Asset Profile**, found under ***Settings*** > ***Asset Hierarchy*** > select an asset > ***Asset Profile***.

<figure><img src="/files/EN3ctnFzSpUH1OWgEQY6" alt=""><figcaption><p>Asset Profile KPI configuration fields</p></figcaption></figure>

## KPI configuration fields

Each asset supports up to three KPI slots (KPI One, KPI Two, KPI Three). For each slot, the following fields are available:

| Field                           | Description                                                                 |
| ------------------------------- | --------------------------------------------------------------------------- |
| **KPI Label**                   | The name displayed for this KPI.                                            |
| **KPI Enabled**                 | Whether this KPI is active and calculated for the asset.                    |
| **KPI Planned Production Time** | The active time window used as the basis for the KPI calculation.           |
| **Exclude Planned Stoppage**    | When enabled, planned stoppages are excluded from the KPI calculation.      |
| **Exclude Planned Changeover**  | When enabled, planned changeover time is excluded from the KPI calculation. |
| **Exclude Unavailable Time**    | When enabled, unavailable time is excluded from the KPI calculation.        |

## Order Card Type

The **Order Card Type** field in the Asset Profile determines which KPI metric is shown on the order card for that asset. Select the KPI you want to display from the dropdown.

<figure><img src="/files/AhHLS2vx7PBvQxUayeeL" alt=""><figcaption><p>Order card displaying calculated KPI</p></figcaption></figure>

## Viewing KPI results

Once configured, KPI values are visible in two places:

* **Order card** – displays the KPI selected in the Order Card Type field
* **Production summary screen** – shows all configured KPIs calculated for the asset

<figure><img src="/files/D9nw5jTge2VwOcEPA9pa" alt=""><figcaption><p>Production summary screen showing all KPIs</p></figcaption></figure>

## How KPIs are calculated

The diagram below illustrates how each KPI type is calculated based on the configured exclusion settings.

<figure><img src="/files/J6Uz8wtAkpZdbJgu5Yid" alt=""><figcaption><p>KPI calculation diagram</p></figcaption></figure>

{% hint style="info" %}
The difference between OEE, OOE, and TEEP lies in what time is included in the denominator. OEE uses planned production time, OOE includes unplanned stoppages, and TEEP uses total calendar time.
{% endhint %}


---

# 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/configuring-kpi-metrics.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.