> For the complete documentation index, see [llms.txt](https://docs.enlyze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enlyze.com/en/concepts/downtimes/categories-and-assignment.md).

# Categories & assignment

After a downtime is automatically detected, the question is: **why** was the machine stopped? Assigning reasons to downtimes makes the difference between a mere availability number and a real analysis.

## Downtime categories

ENLYZE distinguishes three categories of downtimes:

### Planned

Planned downtimes are anticipated interruptions that are part of regular operations. Examples:

* Changeovers and product switches
* Planned maintenance
* Cleaning
* Breaks (when configured as planned downtime)

### Unplanned

Unplanned downtimes occur unexpectedly and are typically the biggest levers for improvement. Examples:

* Technical breakdowns
* Material shortages
* Process errors
* Staffing shortages

### No production planned

This category covers periods when no production was scheduled at all. Examples:

* Weekends and public holidays
* Cancelled or unscheduled shifts
* Plant shutdowns

{% hint style="info" %}
Downtimes categorized as "No production planned" are not considered in the OEE calculation. Only downtimes during scheduled production time affect availability.
{% endhint %}

## Assigning reasons

Assigning a reason to each detected downtime is the basis of every downtime analysis. There are different ways to assign downtime reasons:

### Manual assignment

By default, an employee assigns a reason to each downtime in the ENLYZE App. The configured reasons are organized into categories and groups. A downtime can also be split into multiple segments if different reasons apply (e.g. 30 minutes changeover, then 45 minutes breakdown).

### Automation via shift schedules

Shift times can be configured in ENLYZE. Downtimes outside of shift times are automatically classified as "No production planned". This significantly reduces the manual effort.

### Automation via machine signals

Some machines provide information about the reason for a downtime through the controller (fault codes, status messages). These signals can be evaluated via [computed variables](/en/concepts/understanding-machine-data/variables-and-time-series.md#computed-variables) and automatically assigned to the appropriate downtime reasons.

## Why assignment matters

Without assignment, the analysis only shows **that** the machine was stopped and **for how long**. Only with reasons does the following become visible:

* Which downtime causes occur most frequently (Pareto analysis)
* Where the biggest levers for improvement lie
* Whether changeover times are systematically too long
* How the distribution changes over time

{% hint style="info" %}
How to set up downtime reasons in the ENLYZE App is described under [Defining downtime reasons](/en/production-optimization/downtimes/defining-reasons.md). How to assign reasons is described under [Assign reasons to downtimes](/en/production-optimization/downtimes/assigning-reasons.md).
{% endhint %}

## Related topics

* [Detection](/en/concepts/downtimes/detection.md): How downtimes are automatically detected.
* [Availability](/en/concepts/understanding-oee/availability.md): How downtimes affect OEE.
* [6 Big Losses](/en/concepts/understanding-oee/6-big-losses.md): Downtimes in the context of the six major loss sources.


---

# 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://docs.enlyze.com/en/concepts/downtimes/categories-and-assignment.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.