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

# Plants

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

## Plant Code

This is a unique code with which to identify this plant without the account.

## Timezone

Each plant within an account can have  defined timezone.

When looking at this plant's data in the interface, the times shown will always be local to to plant and not the user's timezone.

## Plant Start Hour

For many plants, midnight is not considers the start/end of a specific day. For example, if a night shift runs until 3am, any production finished before 3am should be counted as part of the previous day.

For this reason, a plant can have a start hour defined. This allows queries for a specific date range to automatically account for this.

Example: For a 3am plant start hour, retrieving all data for 2025-12-25 will have a specific range of `2025-12-25 03:00` to `2025-12-26 03:00`.


---

# 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/configuration/plants.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.