> 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/production/cycle-time-analysis.md).
# Cycle Time Analysis
Understand cycle time performance vs targets, and cycle time variance.
When a schedule is running, Busroot automatically records the cycle time each time a SKU is produced, capturing both average and best times over any given period.
Using this data, Cycle Time Analysis enables you to compare actual performance against targets, identify inefficiencies between stations, and make data-driven refinements for improved productivity.
#### Metrics
* **Quantity -** The number of units produced during the slected time range.
* **Spec. Cycle Time** - The Performance target time set in SKU management.
* **Avg. Cycle Time** - The average time recorded over the selected time range.
* **Best Cycle Time** - The best time achieved during the selected time range.
The Spec. can be easily set to use the Avg. by clicking ‘Ok’ in the Set Avg. as Spec column, aligning performance targets with real production data from the shop floor.
Clicking the SKU name opens the SKU detail page, where you can view a breakdown of cycle times by station. This can help identify whether specific stations or operators are outperforming others and how best practices can be replicated.
---
# 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/production/cycle-time-analysis.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.