# Scheduling Overview

#### **Overview:**

Scheduling in Busroot enables users to set planned production and non-production periods for each station using a flexible, lightweight tool. There are two schedule types: production schedules (linking stations to SKUs) and non-production schedules (linking stations to non-production reasons such as planned maintenance). All schedules have defined start and end times, which can be set either automatically or by operators. The system supports schedule prioritisation and retrospective schedule assignment to review out-of-shift production data retrospectively.

#### **Use Cases and Job Roles:**

* *Production Planning and Execution:*
  * Production Planner: Designs and uploads production schedules.
  * Scheduler: Manages changes, prioritises urgent jobs.
  * Operator: Starts/stops schedules, follows plan on shop-floor tablets.
* *Shift Management and Rapid Plan Changes:*
  * Shift Supervisor: Updates or prioritises schedules in response to dynamic plant conditions.
  * Production Manager: Reviews and adjusts plant-wide schedule adherence.
* *Maintenance & Non-Production Periods:*
  * Maintenance Planner: Enters and manages non-production schedules for planned maintenance.
  * Maintenance Technician: Receives schedule notifications and coordinates work accordingly.
* *Reporting, Quality, and Audit:*
  * Data Analyst: Audits scheduling data for compliance and performance.
  * Quality Manager: Verifies schedule compliance and identifies issues caused by scheduling discrepancies.

#### **Key Functionality:**

* *Production & Non-Production Scheduling:* Assigns stations to SKUs or non-production reasons with clear timing.
* *Priority Schedules:* Allows urgent schedules to be prioritised for immediate execution, visible on operator interfaces.
* *Retrospective Scheduling:* Permits adding or correcting schedules post-event, ensuring accurate production records.
* *Duplicate Management:* Supports multiple schedules for similar station/SKU setups but enforces replacement if identical time slots overlap.
* *Manual and Bulk Schedule Entry:* Schedules can be entered individually or uploaded in bulk via CSV/XLSX.

### Setup 

#### **Priority Schedules** <a href="#prioritising-a-schedule" id="prioritising-a-schedule"></a>

In dynamic operations where plans can change at short notice, certain schedules may need to be completed urgently. Priority can be assigned without the need to edit the planned start time.

Clicking the ‘Prioritise’ button in Schedule Management will move the schedule to the top of the operator interface and highlighted in brighter green, clearly indicating which should be started next. If more than one schedule is prioritised for the same station they will be ordered by planned start. If no longer required priority can be removed by clicking ‘Remove Priority’ and the schedule will be returned to order by Planned Start time.

#### **Schedules Added Retrospectively**

If a production schedule does not exist at the time the station reports production complete, that unit of production will get assigned to the SKU 'unknown'.

If a schedule is then added retrospectively for that time period, Busroot will re-calculate that production and assign it correctly to the SKU in the schedule.

#### **Duplicate Schedules**

Its possible to enter schedules with some duplicate fields. For example if a schedule is entered that has the same Station, SKU and Work Order Ref. as an existing one, but a different Planned Start time, two separate schedules will be entered into Busroot.

Only if a schedule has the same Station, SKU and Planned Start time as another will this replace the existing one.


---

# 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/scheduling/scheduling-overview.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.