# Plant

#### **Context:** 

The plant defines the operational context for all production data (timezone, site).

#### **Importance:** 

Accurate plant setup ensures all time-based data (shifts, schedules, OEE) is correctly synchronised and reported. It is the root for multi-site reporting.

#### Setup: 

Name your plant and set its timezone (e.g., Europe/London for GMT) under Admin > Plant. Each plant should have a unique, recognisable name if you operate multiple locations.

## &#x20;<a href="#plant-code" id="plant-code"></a>

## PLANT SETTINGS <a href="#plant-code" id="plant-code"></a>

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

#### Plant Code <a href="#plant-code" id="plant-code"></a>

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

#### Timezone <a href="#timezone" id="timezone"></a>

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 <a href="#plant-start-hour" id="plant-start-hour"></a>

For many plants, midnight is not considered 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: 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/plant.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.