> 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/archive/customer-guide-to-busroot/glossary-of-busroot-menu-features-and-how-to-use-them/menu-oee-analysis/utilisation-monitoring.md).

# Utilisation Monitoring

## Heatmap <a href="#heatmap" id="heatmap"></a>

Heatmap provides a clear illustration of each stations utilisation across the day or week. Broken down in to windows to show exactly whats happening on the shop floor and where it can be improved.

For stations that are using Downtime Detection Mode > Utilisation Monitoring.

Heatmap windows are 15 mins for Normal Resolution and 5 mins for High Resolution.

These colours represent the Utilisation status of each station in the Heatmap.

* Green - Station has Utilisation greater than 0%
* Red - Station has Utilisation of 0%
* Light Green, Amber and Yellow shades - when set to ‘Normal Resolution - Colour Range’ depending on average Utilisation %
* Purple - Station is not receiving any signal (maybe switched off)
* Blue - Station has a Maintenance Schedule
* Light Grey - Outside of Shift
* Darker Grey - Future Time, when current day or week is selected

A station’s status will only be displayed during shift times.


---

# 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/archive/customer-guide-to-busroot/glossary-of-busroot-menu-features-and-how-to-use-them/menu-oee-analysis/utilisation-monitoring.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.