> 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/detection.md).

# Detection

ENLYZE detects downtimes automatically based on machine data. The principle: a variable that reliably indicates whether the machine is producing is continuously monitored. When its value drops below a defined threshold, a downtime is detected.

## Lead variable and threshold

The foundation of downtime detection is two configuration parameters:

* **Lead variable**: A variable that clearly indicates whether the machine is producing. Typically a speed, throughput, or cycle rate.
* **Threshold**: The limit below which a downtime is detected.

### Example

An extrusion line uses the winder speed as the lead variable. The threshold is configured at 5 m/min:

* Values **below 5 m/min**: The machine is stopped (downtime).
* Values **at or above 5 m/min**: The machine is producing.

Detection is accurate to the second and fully automatic. No manual input is required.

### Typical lead variables by machine type

| Machine type   | Typical lead variable        |
| -------------- | ---------------------------- |
| Extrusion      | Haul-off speed, winder speed |
| Printing press | Line speed                   |
| Assembly line  | Pieces per minute            |
| Packaging      | Cycle time, piece counter    |

## Minimum duration

To avoid short-term "flickering" (e.g. when speed briefly drops below the threshold and immediately rises again), a minimum duration can be configured. Only downtimes lasting longer than the minimum duration are recorded.

## Boolean variables

In addition to numerical variables, Boolean variables (True/False) can also be used as lead variables. In this case, you configure whether `True` or `False` represents a downtime.

## Advantages of automatic detection

* **Objective**: No subjective assessment by employees.
* **Gap-free**: Every downtime is captured, even at night or on weekends.
* **Second-accurate**: Precise start and end times instead of estimates.
* **Automatic**: No manual effort for basic tracking.

{% hint style="info" %}
How to configure downtime detection in the ENLYZE App is described under [Setting up OEE tracking](/en/production-optimization/oee.md).
{% endhint %}

## Related topics

* [Categories & assignment](/en/concepts/downtimes/categories-and-assignment.md): How detected downtimes are assigned reasons.
* [Availability](/en/concepts/understanding-oee/availability.md): How downtimes affect OEE 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://docs.enlyze.com/en/concepts/downtimes/detection.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.