# Reasons

#### **Context:** 

User-defined codes for downtime or non-productive time.

#### **Importance:** 

Accurate reason setup allows root cause analysis, supports Pareto charts (on OEE Analysis page), and improves loss categorisation for continuous improvement priorities.

#### Setup:

Customise your downtime and non-production reasons. Edit, delete, or add entries to match your operational context. This improves all stoppage and efficiency reporting.

## Reasons Settings 

#### Parent Reason <a href="#parent-reason" id="parent-reason"></a>

Causes can be added in multi-levels. Select whether this is a Top-level Cause or which group it belongs to.

#### Description <a href="#description" id="description"></a>

Enter a short description for the reason.

#### Type <a href="#type" id="type"></a>

Finally select if you would like this recorded in Busroot as Downtime or as a non-production reason. Non-production will not count as unplanned downtime and will therefore will not negatively impact your OEE, as it is considered planned maintenance.&#x20;

#### REASON MANAGEMENT

<figure><img src="/files/P9KJJ5oWQbXm2miD0cZC" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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.output.industries/admin/reasons.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.