> 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-availability.md).

# Two Steps to Availability

## Configuring shifts

Configure **shifts** for your assets. This way TilliT knows when you should and shouldn't be in production. Any downtime outside of production hours will not penalize your availability. This defines what 100% Availability will be.

### 1. Creating Shift Templates:

This allows you to set up shift patterns on the asset to set a standard to be compared against for when an order or an asset is supposed to be running and vice versa.

See [Creating a Shift Template](/tillit/knowledge-base/setting-up-tillit/asset-hierarchy/shifts/shift-patterns.md) for guide on configuring.

### 2. Creating Calendar

Follow [Calendar](/tillit/knowledge-base/setting-up-tillit/asset-hierarchy/calendar.md) and [Calendar item](/tillit/knowledge-base/setting-up-tillit/asset-hierarchy/calendar/calendar-item.md) to create a calendar and a calendar item to set a period of time that your shift templates apply to.

**Important:** Afterwards, go the the asset(s) that this calendar apply to and choose the calendar you just created in the asset's basic information.

<figure><img src="/files/dgSl1eT6A8hu42skkp7A" alt="" width="461"><figcaption></figcaption></figure>

### 3. Creating Order Templates

Creating Order Templates will allow you to configure default data types for when an asset is in Downtime or Changeover. This helps classifying whether the change is PLANNED, UNPLANNED, or something else.

For example if an asset's stoppage is UNPLANNED, then this will negatively affect the Availability score.

## Adding asset's data

For this part, we need to ingest **machine statuses** into TilliT. For best results, you need to read local data sources with a TilliT Edge device or Integrate via API/MQTT.

See Equipment Status Templates inthe [Data Tag Templates](/tillit/knowledge-base/setting-up-tillit/edge/data-tags/data-tag-templates.md) for ingesting via edge or Publishing Order Progress from [MQTT Integration](/tillit/knowledge-base/setting-up-tillit/integrations/mqtt-integration.md) for using MQTT. When you do experience a stoppage event, attach a **reason code** to understand what caused the downtime via a machine tag or activity submission.

Classify your reason codes as planned or unplanned to only measure the downtime you want to effect Availability. See [Option list](/tillit/knowledge-base/setting-up-tillit/activity-templates/activity/elements/data-types/option-list.md)and [Data Tag Templates](/tillit/knowledge-base/setting-up-tillit/edge/data-tags/data-tag-templates.md) .

Downtime during your **order changeover** will automatically be measured as planned until scheduled changeover duration is exceeded. At this point, unplanned downtime will start to negatively effect your availability.


---

# 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-availability.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.