> 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/workflows/basic-utilisation-monitoring.md).

# Basic Utilisation Monitoring

Using a simple threshold on station productivity to identify prolonged periods of stoppage, without the need to input production schedules.

### Benefit

Identify and rectify unnecessary equipment stoppages.

### Setup

For each station to be monitored, set a utilisation downtime threshold. This is the minimum number of minutes that should be considered as excessive downtime of the station.

If you do not intend on inputting production schedules, ensure the setting 'Assume All In Shift Time is Planned Production' is set to true.

### Daily Workflow

1. Ensure a Non Production Schedule is entered for any stations that aren't planned to run to prevent downtime being wrongly recorded.
2. Busroot will automatically detect downtime based on the utilisation threshold settings.
3. Production manager will receive a notification that the station is stopped.
4. Operator or production manager will attribute a cause for the stoppage.
5. During team meetings, the previous days downtime reasons are reviewed and discussed.


---

# 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/workflows/basic-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.