> 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/production-optimization/downtimes.md).

# Downtimes

ENLYZE detects machine downtimes automatically based on machine data and provides tools for structured analysis. This section covers the entire downtime workflow: from automatic detection through defining reasons to assigning them.

## Downtime workflow

The downtime workflow in ENLYZE consists of three steps:

1. **Automatic detection:** ENLYZE continuously monitors your machines and automatically detects downtime events based on configured parameters. Learn more: [Automatic detection](/en/production-optimization/downtimes/detection.md)
2. **Define downtime reasons:** Create a structured catalogue of downtime reasons, organized into planned, unplanned, and no production planned categories. Learn more: [Defining downtime reasons](/en/production-optimization/downtimes/defining-reasons.md)
3. **Assign reasons:** Assign reasons to detected downtimes to enable meaningful analysis and reporting. Learn more: [Assign reasons to downtimes](/en/production-optimization/downtimes/assigning-reasons.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:

```
GET https://docs.enlyze.com/en/production-optimization/downtimes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.