Downtime evidence

A run-minute total tells the team how long production ran. Downtime evidence supplies the intervals and reasons needed to investigate the rest of the period. Production Operator records the start and end of each stop, adds a reason code and identifies whether the stop was planned.

Every interval links to a production window. Production Planner can therefore discuss a stopped machine in the context of the period being reviewed. A reason such as a material wait needs a different operating response from a planned break, even when the elapsed time is similar. Keep that distinction clear before comparing the windows.

• Interval capture. Production Operator records when the stop began and ended. Use the observed times even when the explanation is completed later, so the review can reconstruct the period accurately.
• Stop classification. The operator marks planned stop as Yes or No and enters the agreed reason code. Production Planner resolves disagreements over classification before using a reason-based comparison to direct follow-up work.
• Window review. Quality Reviewer examines the selected window and observation alongside its downtime evidence. The review checks coverage and context; stock release follows its own production and batch decision.

Choose a reason vocabulary that operators can use consistently. Decide who resolves unclear causes and how a stop spanning the window boundary is handled. Agree how planned breaks affect planned minutes, and how overlapping stop records are reviewed before elapsed time is summarized.

The plant should also decide where maintenance work is managed. If a stop requires a repair, connect the maintenance system through an agreed process and keep the downtime explanation understandable to the production team. A resource marked Maintenance informs planning, while the maintenance team manages repair activity in its own operating system.

Rehearse an unplanned stop on Press A from 10:10 to 10:25. Production Operator selects the morning window, records the reason as a material wait and marks planned stop as No. Production Planner checks the interval against the run observation before discussing the loss with the shift team.

Next, add a second rehearsal entry covering part of that same stop. Ask the planner to identify the overlap and settle how the report should treat it. Then rehearse a stop that ends after the production window closes. The team should agree its allocation and preserve a clear explanation before using the totals in a resource comparison. The aim is a repeatable review decision, with times and reasons that another shift can understand.

• Unplanned Downtime — Unplanned stop intervals with their reason and production window.
• Planned Production Windows Queue — The time boundary and resource used to assess each recorded stop.

Follow capture run evidence, then review window coverage. Discuss external maintenance handoffs in integrations.