# Downtime Detection ### Why do we use the word 'issue' in Busroot? For the sake of brevity, we want a single word to describe unplanned downtime in our data. The word 'stop' or 'downtime' cannot be used on their own without creating confusion. Both words can be used to describe planned and unplanned stoppages. Differentiating between planned and unplanned stoppages is a key element of measuring manufacturing performance and OEE, therefore we use the word 'issue' to make it clear we are referring specifically to unplanned downtime. ### ### Acknowledge When a station has unexpectedly stopped production, Acknowledge is the first action that must be taken. To inform colleagues that the issue is under control and steps are being taken to resolve it. ### Estimate Submit an estimated time to resolve an issue once a solution is found. #### Estimate Threshold Notification Groups ### Escalate If a solution can't be found, Escalate raises the status of the issue to bring in the right people to help. This can be triggered either manually or automatically by Busroot, if an Estimate is not entered within a time limit or has expired. #### Escalation Groups #### Escalation Rules/Limits Define the time between when a Station stops and is automatically Escalated by Busroot. ### Watch Issues This feature allows you to track the progress of an issue. ### Causes Submit a downtime cause from a list of commonly occurring issues. #### Multi-level #### User Managed #### Fixed --- # 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/archive/use-busroot/oee/downtime-detection.md?ask= ``` 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.