# Speed Loss and Micro-Stoppage Calculator

> Source: https://netray.co/tools/speed-loss-and-micro-stoppage-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Separate the performance loss in OEE into reduced speed and minor stops, and see the parts each one costs per shift.

## Category

mes-shop-floor

## Industry

Discrete Manufacturing

## Audience

- Production supervisor
- Process engineer
- Continuous improvement manager

## Tool

**Kind:** calculator

**Inputs:**

#### Ideal cycle time

**Key:** ideal_cycle

**Type:** number

**Default:** 12

**Min:** 0.1

**Step:** 0.5

**Unit:** seconds/part

#### Average actual cycle time while running

**Key:** actual_cycle

**Type:** number

**Default:** 14.5

**Min:** 0.1

**Step:** 0.1

**Unit:** seconds/part

**Help:** Average time per part when the machine is actually cycling.

#### Run time in the period

**Key:** run_hours

**Type:** number

**Default:** 7

**Min:** 0

**Step:** 0.25

**Unit:** hours

**Help:** Time the machine was scheduled and not in a recorded stop.

#### Minor stops in the period

**Key:** stop_count

**Type:** number

**Default:** 35

**Min:** 0

**Step:** 1

**Unit:** stops

**Help:** Stops too short to be logged as downtime, typically under 5 minutes.

#### Average duration of a minor stop

**Key:** stop_sec

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** seconds

**Outputs:**

#### Run time

**Key:** run_sec

**Expr:** run_hours * 3600

**Format:** number

**Description:** In seconds.

#### Time lost to minor stops

**Key:** stop_total

**Expr:** stop_count * stop_sec

**Format:** number

**Description:** In seconds.

#### Time actually cycling

**Key:** net_sec

**Expr:** max(run_sec - stop_total, 0)

**Format:** number

**Description:** In seconds.

#### Parts produced

**Key:** parts

**Expr:** net_sec / actual_cycle

**Format:** integer

#### Minor stop loss

**Key:** stop_loss

**Expr:** stop_total / run_sec * 100

**Format:** percent

**Description:** Share of run time lost to short stops.

#### Reduced speed loss

**Key:** slow_loss

**Expr:** net_sec / run_sec * (1 - ideal_cycle / actual_cycle) * 100

**Format:** percent

**Description:** Share of run time lost to cycling slower than ideal.

#### Performance rate

**Key:** performance

**Expr:** parts * ideal_cycle / run_sec * 100

**Format:** percent

**Primary:** true

**Description:** Equals 100 minus the two losses above.

#### Parts lost versus ideal

**Key:** parts_lost

**Expr:** run_sec / ideal_cycle - parts

**Format:** integer

**Primary:** true

**Chart:**

#### Performance rate vs actual cycle time

**Type:** line

**X:** actual_cycle

**From:** 12

**To:** 18

**Steps:** 25

**Series:**

- performance

**Disclaimer:** Performance is capped at 100 percent in practice. A value above that means the ideal cycle time is set too slow and should be revalidated.

## Content

**Intro:** Performance is the least understood part of OEE. It hides two different problems: the machine running slower than its ideal cycle, and the many short stops nobody logs. This calculator separates them, so the team knows whether to chase tooling and parameters or jams and starvation.

**Sections:**

#### How to use it

**Body:** Take a shift or a day. Enter the ideal cycle time, the average cycle time while running, and the run time after recorded downtime. Then count minor stops, those too short to appear in your downtime log, and their average duration. The calculator splits the performance loss into a stop component and a speed component, shows the performance rate and counts the parts lost against the ideal. Count stops from machine counters or video for a few shifts rather than relying on memory.

**Bullets:**

- Use a validated ideal cycle time, not a guess
- Sample at least three shifts to find the average stop duration
- Record minor stops with a reason code where possible

#### Formula and logic

**Body:** Performance equals parts produced times ideal cycle time, divided by run time. When stops remove time from cycling, parts equal cycling time divided by actual cycle time. That expands to: one minus the stop share, minus the cycling share times one minus ideal over actual. So performance equals 100 minus stop loss minus speed loss, and each loss is shown separately. This is the standard treatment of reduced speed and minor stops, two of the six big losses. Keep the definitions consistent over time, otherwise trends mislead.

#### Worked example

**Body:** A 7 hour run with a 12 second ideal and 14.5 second actual cycle, plus 35 stops averaging 40 seconds. Stops cost 1,400 seconds, about 5.6 percent. The machine cycles for 23,800 seconds, making roughly 1,641 parts instead of an ideal 2,100. Speed loss is about 16.3 percent, so performance is 78.2 percent and 459 parts are lost. Here the slow cycle is the larger lever: check feeds, speeds, and conservative operator settings before chasing stops.

#### Common mistakes

**Body:** Setting the ideal cycle time to what the machine currently achieves hides speed loss completely and makes OEE look healthy. Another is logging stops only above five minutes, which pushes dozens of small stops into performance without any evidence. Operators also slow machines down on purpose to avoid stops, so compare speed and stop losses together before declaring a fix.

**Bullets:**

- Do not set ideal equal to current average
- Do not ignore stops under five minutes
- Watch for speed being lowered to hide stops

**Cta:** If machine counters or PLC signals already exist, we can help bring cycle and stop data into a read-only view alongside your ERP production reporting.

**Faq:**

#### What counts as a micro-stoppage?

**Answer:** A short interruption, usually under about five minutes, that the operator clears without a maintenance call: a jam, sensor trip, or starved feeder. They rarely get logged as downtime, so they land in performance loss.

#### Why is my performance over 100 percent?

**Answer:** The ideal cycle time is set too slow, or counts are wrong. Revalidate the ideal against design capacity or best demonstrated rate and fix the reference before using OEE for decisions.

#### How do I get the average actual cycle time?

**Answer:** Divide cycling time by parts produced, where cycling time is run time minus the time lost to minor stops. Machine counters and timestamps give this reliably; a stopwatch gives a rough check.

#### Which loss should I attack first?

**Answer:** Start with whichever is larger in your result, and with the cheapest cause. Speed loss often responds to parameter and tooling changes; minor stops usually respond to cleaning, standards and sensor fixes.

## Search terms

oee performance loss calculator, speed loss calculator, micro stoppage calculator, minor stops oee, reduced speed loss, ideal cycle time vs actual cycle time, performance rate calculation, hidden factory oee

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json