> 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/technical-onboarding/release-notes/2026/week-28-or-2026.md).
# Week 28 | 2026
This release introduces three new features: Schedule Capacity planning, Manual Downtime logging, and Reason Trends analysis. It also brings enhancements to the Trend Viewer, Pulse Chart, and Operator Tablet.
#### New Features
**Manual Downtime**
Operators can now log downtime manually from the tablet, with a mandatory reason. This is useful for stations where downtime is determined by an operator rather than an automatic signal, or where a machine is still running but under investigation. While a manual downtime is active, all production and utilisation recording is blocked to keep reporting accurate. Rollout is controlled per account via a feature flag.
**Schedule Capacity**
A new page that shows whether stations are under or over-scheduled at a glance. Accessible from the main menu, it provides a weekly overview with colour-coded capacity cells and CSV export. This feature is currently in development and may be refined based on feedback.
**Reason Trends**
A new charting capability in the Trend Viewer for analysing Downtime and Non-Production reasons over time. Includes filtering by individual reason, with searchable tree-select for easy navigation.
#### Improvements
**Work Order Search** — The Gantt Chart and Schedule List now support searching by work order reference. Toggle between filter mode and search mode to quickly find schedules by their work order ref.
**Trend Viewer**
* Grouped metrics — Metrics are now organised in a searchable tree-select dropdown with icons on group headings, making it easier to find the right metric
* OEE enhancements — Updated OEE metric display and axis labelling
* Station selection limit — Selection is now limited to 5 stations, with a clear message explaining the limit
**Pulse Chart**
* Grouped metrics — The metrics menu now uses a tree-select dropdown, consistent with the Trend Viewer
* Sidebar guide — Removed an outdated reference to retrospective scheduling
**Operator Tablet**
* Station list legend — Added colour indicators to the station list for quick visual reference
* Unreported downtime icon — Re-instated the unreported downtime indicator on the tablet
* Station details on reason screen — Station information is now shown when providing a downtime reason
* PPC Override for Ad-Hoc schedules — Ad-hoc schedules now support parts-per-cycle override
* Header styling — Standardised font sizes, spacing, and border radius across tablet headers
**Trend Viewer & Pulse Chart**
* Multi-select — Replaced the close button with a clearer "clear selection" action in metric dropdowns
**Production by Schedule**
* Back button — Added a back button to return to the Schedule List with filters preserved
**Downtime Analysis**
* Percentage bars — The downtime analysis treetable now displays percentage bars for easier visual comparison
**Station & SKU Naming**
* Station Code and Name — Now displayed consistently across all areas of the platform
* SKU Code and Name — Now displayed consistently across all areas of the platform
**Schedule Upload**
* Error messages — Clearer, more descriptive error messages when uploading schedules fails
**Bug Fixes**
* Pulse Chart tooltip — Fixed the tooltip extending off the edge of the screen
* Reason deletion — The system now falls back to the reason code when a reason is deleted, preventing display errors
---
# 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/technical-onboarding/release-notes/2026/week-28-or-2026.md?ask=&goal=
```
`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.