# Week 17 | 2026

#### Featured improvement: **Target Quantity on Ad-Hoc Schedules** 

Operators can now set a target quantity when creating ad-hoc production schedules from the tablet, unlocking the added features available on planned schedules. This enables:

* **Real-time progress tracking** — see live completion percentage and\
  units remaining during ad-hoc runs (eg. Cockpit)
* **Production forecasting** — estimated completion times are now\
  available for ad-hoc schedules, just as they are for planned orders (eg. Production Progress Dashboard)

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

#### General Updates:

* **Utilisation Improvements** — Utilisation in the Hierarchy Explorer has been broken down into clearly defined columns — Total Considered Time, Productive Time, and Utilisation % — with hover tooltips explaining what each value represents and how it is calculated. The Pulse Chart also now includes a new hover tooltip.
* **Trend Viewer — Asset Utilisation** — The Asset Utilisation metric now reports in productive time (in the chosen Duration Format eg. Mins or Hours, Mins) instead of percentage. Utilisation % is now included as a standard summary metric across all Trend Viewer metrics.
* **Configurable Week Start Day per Plant** — Each plant can now have its own week start day, so weekly reports and date ranges align with your actual production week.
* **Station Filtering on Analysis Pages** — Cycle time analysis, production by SKU, and production by work order reference pages now support filtering by group and individual stations.
* **Date Range Filtering on Station Notes** — Station notes can now be filtered by date range, with CSV exports respecting the selected period.

<br>


---

# 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/technical-onboarding/release-notes/2026/week-17-or-2026.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.