> 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/live-monitoring/production-progress.md).

# Production Progress

#### **Overview:**

The Production Progress page in Busroot provides a live, visual snapshot of how current production schedules are progressing against set targets. Designed for shop floor operators and production managers, it enables real-time monitoring of output at each station. Immediate visibility helps keep teams on track, spot delays, and quickly address issues to maximise productivity and schedule adherence. The value is in delivering up-to-date information that supports timely, data-driven shop floor decisions.

#### **Use Cases:**

* **Operator:** Wants to see if their current job is ahead or behind target and how much work remains in the shift.
* **Production Manager:** Needs to monitor all open schedules across stations, spot bottlenecks, and adjust resource allocation in real time.
* **Supervisor:** Uses the page to quickly review daily performance during stand-up meetings or changeovers to keep everyone aligned.

#### **Functionality:**

* **Schedule List:** Shows all running and upcoming production schedules, ranked by planned start time (or alphabetically). Schedules update in real time and can be filtered by status.
* **Progress Chart:** Visual graph displays quantity completed versus target for each schedule, highlights if production is on-track/behind, and provides estimated time remaining.
* **Manual & Automatic Entry:** Units produced can be captured automatically from the machine or manually entered via operator tablets.
* **Schedule Controls:** Allows operators or managers to start, stop, or complete schedules, trigger progress updates, and refine performance targets on the fly.
* **Visibility Rules:** Only schedules with a set quantity/end time show on this page; ongoing (continuous) schedules are excluded. Completed or ended schedules are displayed briefly before being cleared from the board.
* **Prerequisites:** Requires setup of station schedules, performance targets for SKUs, and configuration of the relevant tablets/displays. Data accuracy depends on correct schedule input and timely manual or automatic updates.

#### **Data Setup:**

* Add SKUs and SKU groups with cycle time and line speed values via Admin > Management > SKU.
* Establish production schedules, assigning SKUs and targets.
* Configure manual or automated unit entry on operator tablets or machine integrations.

#### **Key Formulas:**

* Progress % = (Units Completed / Target Units) × 100
* Estimated time remaining = (Target - Completed) × Cycle Time (seconds)

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


---

# 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:

```
GET https://docs.output.industries/live-monitoring/production-progress.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.