> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/downtime/downtime-analysis.md).

# Downtime Analysis

#### ANALYSING THE DATA

Downtime analysis goes one level deeper on from the downtime list. It will group stoppages by the parent reason and allow you to dropdown and see the various reasons assigned to that parent reason. You can view the number of stoppages for each reason and the total downtime. 

In the final column you can quick select by using the buttons above the table (highlighted with the green arrows in the image below). This allows you to view the downtime as a value of your choosing. It can be lost production (and the units you could've made based on the SKU cycle time), the cost of time using the monetary value in your Admin > Station > Downtime settings, or the energy that has been wasted during this period, if you track energy. 

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


---

# 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.output.industries/downtime/downtime-analysis.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.