> 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/archive/workflows/performance-monitoring.md). # Performance Monitoring Monitor the speed (performance) of assets against target speeds for a given production schedule. ### Benefit Know when a line is running slow and what's caused it, to be able to prevent future issues. ### Setup A production schedule should be added for the planned duration or quantity of production. All SKUs to be produced must have a Performance Target set, this is the ideal rate that the SKU should be produced, based on Cycle Time, Units per Minute, Units per Hour or an Independent Process Speed. For stations that produce the same SKU every day a schedule isn't necessary, instead a Performance Target must be set at station level. A tablet for each station to be monitored. ### Daily Workflow 1. If current speed drops below 80% of Performance Speed Target, a 'Slow' type issue will be created. 2. Production manager will receive a notification via email or by viewing the cockpit that the station is running slow. Operator will see an alert on the tablet informing them that the station is running slow. 3. Either operator or production manager assigns a cause to the issue. 4. During team meetings, the previous days Slow causes are reviewed and discussed. Allowing solutions to be found, preventing further issues. --- # 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/archive/workflows/performance-monitoring.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.