# Micro Stop Log Worksheet for Short Stoppages > Source: https://netray.co/tools/micro-stop-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Tally minor stops by cause on the line, convert them to lost minutes, and export a clean log for OEE analysis. ## Category mes-shop-floor ## Industry Discrete Manufacturing ## Audience - Continuous improvement manager - Production supervisor - Process engineer ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Time window **Key:** time **Type:** text #### Machine **Key:** machine **Type:** text #### Cause **Key:** cause **Type:** select **Options:** - Jam - Sensor fault - Material feed - Part missing - Tool wear - Operator adjust - Upstream starve - Downstream block - Other #### Seconds per stop **Key:** duration **Type:** number **Unit:** s #### Number of stops **Key:** count **Type:** number #### Total seconds **Key:** total_sec **Type:** number **Expr:** duration * count **Format:** number #### Lost minutes **Key:** lost_min **Type:** number **Expr:** duration * count / 60 **Format:** decimal **Rows:** #### Jam **Time:** 06:00-07:00 **Machine:** Press 4 **Duration:** 25 **Count:** 6 #### Sensor fault **Time:** 07:00-08:00 **Machine:** Press 4 **Duration:** 40 **Count:** 3 #### Material feed **Time:** 08:00-09:00 **Machine:** Packer 2 **Duration:** 18 **Count:** 11 #### Downstream block **Time:** 09:00-10:00 **Machine:** Packer 2 **Duration:** 55 **Count:** 4 #### Operator adjust **Time:** 10:00-11:00 **Machine:** Press 4 **Duration:** 30 **Count:** 5 **Totals:** #### Total stops **Key:** count **Agg:** sum **Format:** integer #### Total lost minutes **Key:** lost_min **Agg:** sum **Format:** decimal **Summary:** #### Average stop length **Key:** avg_stop **Expr:** if(gt(sum_count,0), sum_lost_min * 60 / sum_count, 0) **Format:** number **Description:** Seconds per stop, across all rows. **Notes:** Use a consistent threshold for what counts as a micro stop, for example any stop under five minutes that the operator clears without maintenance help. Record counts by tally mark on the line and enter them at the end of each hour. ## Content **Intro:** Short stops are the loss that rarely appears in a downtime report, because nobody opens a work order for a ten second jam. Together they can cost more output than a few long breakdowns. This log gives operators a simple way to count them by cause and convert the count into lost minutes. **Sections:** #### How to use the log **Body:** Place a printed copy of the cause list at the machine and have the operator make tally marks during the shift. At the end of each hour, enter the time window, the machine, the cause, the average seconds per stop and the number of stops. The sheet multiplies the two to give lost seconds and minutes, and the summary shows the total number of stops and the average length. Review the log with the team at the shift start meeting, and pick the top cause for a root cause session. #### Why micro stops matter **Body:** In most OEE conventions, stops below a set threshold are not counted as downtime but as a reduction in speed, so they show up in the performance factor. That is why a line can report high availability and still run well below its ideal rate. Logging them separates the true cause of the performance loss from slow running, which needs a different fix such as machine tuning or a revised standard rate. **Bullets:** - Typical threshold: under five minutes, no maintenance call - Count of stops matters as much as duration - Frequent stops often point to a small upstream defect #### Reading the numbers **Body:** Sort the causes by lost minutes and also by count. A cause with many very short stops, like a feed jam, is usually a design or setup issue, while a cause with few long stops may deserve a downtime work order. Compare the average stop length with the cycle time: if the average stop is shorter than a few cycles, automatic recovery or a better sensor may remove it. Track the weekly total to see whether fixes hold. #### Common mistakes **Body:** The usual failure is a cause list that is too long, so operators pick Other. Keep nine or fewer categories and review Other every week. Another mistake is mixing micro stops into the formal downtime log, which double counts the loss. Decide which log owns each event, write the rule on the sheet, and keep it the same across shifts so comparisons are fair. **Cta:** If your machines already send counts and stop signals to an MES or ERP, we can turn that signal into this log without manual tallying. **Faq:** #### What counts as a micro stop? **Answer:** There is no universal rule. Many plants use any stop shorter than about five minutes that the operator clears without a maintenance call. Choose a threshold, write it on the sheet, and apply it consistently so trends are comparable. #### Do micro stops affect availability or performance in OEE? **Answer:** Under the common convention they reduce the performance factor, because the machine was scheduled and technically running. If you count every stop as downtime, they reduce availability instead. Either is valid when applied consistently. #### How often should operators enter data? **Answer:** Tally during the hour and enter once per hour or at least once per half shift. Entering from memory at the end of a shift loses detail and tends to under count small stops. #### Can I export this log? **Answer:** Yes. Export to Excel, CSV or PDF at any time. The calculations run in your browser and nothing is stored on a server. ## Search terms micro stop log, minor stoppage log template, short stops tracking sheet, speed loss log excel, line stoppage tally sheet, small stops oee, minor stops worksheet --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json