# Understand the interruptions behind the production total. Use production monitoring and manufacturing analytics to connect shift totals with jobs, machine states, interruptions and the evidence behind an explanation. Canonical: https://vieox.com/insights/manufacturing/production-flow/ Publisher: VIEOX Published: 2026-10-20 Updated: 2026-10-25 ## How can a manufacturing team investigate lost production time more clearly? Choose a defined interruption, place it within the job and process sequence, and compare the equipment record with operator and planning context. Keep the observation distinct from its explanation, then agree the next question and who will examine it. A production total is a useful opening to a review. The discussion becomes more valuable when the team can move from that total to the jobs, events and circumstances behind it, without repeatedly reconstructing the same story. ## Define the work before comparing the shift. Begin with what the selected machine or line was expected to do. Identify the job, product, relevant revision and planned operating period. A shift that includes a new setup, short runs and inspection holds cannot be understood simply by placing its output beside a long, steady run. Write down the comparison the team actually wants to make. Are you reviewing the duration of a particular setup, a recurring interruption after a certain operation, or the flow of work between two stages? ## Read the process as a sequence of events. For the period under review, assemble the available start, stop, wait, restart and completion records. Ask whether timestamps describe the event itself or the later recording of the event. If a period is uncertain, retain that uncertainty rather than assigning a precise duration that the evidence cannot support. NIST's shop-floor research addresses collection and re-use of manufacturing equipment data. A stoppage review can apply that idea by preserving context for another person to revisit the event. Keep the description short enough to review together: what happened first, what changed next, and what evidence shows that the work resumed. A clear sequence often exposes the next useful question before any elaborate analysis is needed. Sources: [1](https://www.nist.gov/publications/connecting-deploying-and-using-smart-manufacturing-systems-test-bed) ## Look at the work on either side of the machine. A machine may be the place where an interruption is recorded while the question lies in the work arriving before it or leaving after it. Bring in the relevant material movement, release, inspection and downstream availability records. Ask what those records can establish about this event, rather than treating every nearby event as a cause. NIST's manufacturing information research recognises feedback between production and quality activities. A practical review can similarly keep inspection context connected to the production period it concerns. Use that connection carefully. An inspection hold is an operational state; the reason for that hold and its disposition belong to the quality process. Preserve both the timing and the responsible person's explanation so the production discussion does not redefine the quality decision. Sources: [2](https://www.nist.gov/programs-projects/digital-thread-manufacturing) ## A pause after changeover deserves a closer look. Hypothetical example: an assembly line records repeated waits during the first part of a product run. The initial explanation is that the changeover takes too long. The team instead separates the changeover period from the waits after production has started. The available notes show that several waits coincide with requests for a different component presentation. That is a lead for investigation, not proof of the cause of every wait. Production and material-handling colleagues compare similar runs, identify which events share the circumstances and note the occasions that do not. The resulting question is more specific: what needs to be confirmed about the start-of-run preparation for this product? It can be assigned and reviewed. The example illustrates a way of asking better questions; it is not a customer result or an asserted diagnosis. ## Give manufacturing analytics a fair comparison. When events appear to recur, check the basis for grouping them. Product, equipment, shift conditions and recording definitions may have changed. A category such as material wait can contain several different situations. Examine representative events before treating their combined duration as a single problem. Retain an explanation's status. It may be a first suggestion, supported by some records, challenged by another observation or confirmed through the site's review. Keeping that progression visible makes the conclusion easier to question and improves the value of the record for later work. ## Give the review a concrete next step. Close with the issue under investigation, the evidence already considered, the remaining uncertainty and the person responsible for the next review. Revisit the same question after an agreed action or further observation. If the explanation changes, record why it changed. A useful conversation with VIEOX can start with one recurring interruption and the records currently used to explain it. Tell us which part takes the team most effort: finding the relevant period, connecting the job, understanding the equipment state or keeping the follow-through clear. That gives us a specific information problem to explore together. ## Practical starting points - Select one interruption with a clear equipment and time boundary. - Place it within the actual job and process sequence. - Compare machine records with the relevant operator and planning notes. - Check alternative explanations and keep incomplete information visible. - Agree an owner, a next question and a point for reviewing the answer. ## Questions, answered ### Should every short stop be investigated individually? Choose the detail according to the review question. Individual examples can help establish whether a grouped category is meaningful. Once the grouping is sound, the team can decide which events deserve closer attention. ### Can an alarm message be used as the downtime cause? It can be part of the evidence. Record what the message establishes, when it appeared and what else was happening. The explanation still needs to account for the operating sequence and the observations of the people involved. ### What should a real-time production monitoring dashboard show? Show the relevant machine or line, job, production period, agreed count definitions and the freshness of the latest information. Let readers locate interruptions and their supporting records. Keep a missing update distinguishable from a stopped machine, and separate a live status from a confirmed explanation. Judge the dashboard by the decisions the team can support with it. ## Sources and further reading - [NIST — Connecting, Deploying, and Using the Smart Manufacturing Systems Test Bed](https://www.nist.gov/publications/connecting-deploying-and-using-smart-manufacturing-systems-test-bed) - [NIST — Digital Thread for Manufacturing](https://www.nist.gov/programs-projects/digital-thread-manufacturing) ## Related reading - [Manufacturing overview](https://vieox.com/industries/manufacturing/) - [Equipment condition and maintenance](https://vieox.com/insights/manufacturing/equipment-condition/) - [Investigating a production stop](https://vieox.com/insights/investigating-production-downtime/) - [Production visibility](https://vieox.com/solutions/production/)