Machine Utilization by Shift for Small Manufacturers: How to Compare Runtime, Idle Time, and Minor Stops Across Crews to Recover Lost Capacity

Most small manufacturers know which machines are busy overall. Far fewer know whether first shift is carrying second shift, whether one operator group is losing an hour a day to short stops, or whether “busy” machines are actually sitting idle between jobs. That blind spot matters because machine utilization averaged across the whole day can hide the exact crew, handoff, or scheduling gap that is quietly consuming your capacity. For a complete overview, see our manufacturing execution system software guide.

If you want to recover output without buying another machine, start by breaking utilization down by shift and operator group. When you compare runtime, idle time, and minor stops across crews, patterns become visible fast: one shift may run longer uninterrupted cycles, another may spend more time waiting on material, and another may be repeatedly interrupted by tooling adjustments, inspections, or small resets. Once you can see those differences clearly, you can fix the causes instead of arguing about them.

Why overall machine utilization is not enough

A machine-level utilization number for the week is useful, but it is too blunt for daily management. A machining center showing 72% utilization may sound acceptable until you split that number by shift and find first shift at 84%, second shift at 63%, and weekend coverage at 41%. The machine itself is not the root cause. The gap is usually driven by the way labor, material, setups, supervision, maintenance support, and job release timing change from crew to crew.

Looking by shift helps answer practical questions such as:

• Are jobs staged and ready at the start of every shift?
• Do some crews spend more time waiting for first-piece approval?
• Are short stoppages clustered around operator changeovers?
• Is one shift absorbing most setups while another shift benefits from longer run time?
• Are staffing decisions creating avoidable machine idle time?

This is also where utilization and scheduling connect. If jobs are released late or work queues are inconsistent, the problem may look like poor operator performance when it is actually a planning issue. Shops already tracking planned versus actual timing should connect this analysis to schedule performance. See planned vs. actual start and finish times by work order and planned vs. actual completion by work order for the planning side of the picture.

Define the three time buckets clearly

Before comparing crews, make sure everyone uses the same definitions. If one supervisor codes a five-minute sensor reset as downtime and another calls it runtime loss, your shift comparison will be noisy and hard to trust.

Runtime

Runtime is the period when the machine is actively producing parts or executing a valid cycle. For many shops, this is the most straightforward signal because it can often be captured from cycle start and cycle complete events.

Idle time

Idle time is available production time when the machine is not running and no valid cycle is active. Common causes include:

• Waiting for the next job
• Waiting for material, tooling, or fixtures
• Operator absence
• Inspection hold
• Forklift or crane delays
• Unclear job priorities

Idle time is often the biggest hidden capacity drain in small shops because it looks harmless in short bursts. Ten minutes here and twelve minutes there can remove hours from a week.

Minor stops

Minor stops, also called micro-stoppages, are short interruptions that do not always get logged in traditional downtime systems. These may include:

• Brief alarms or resets
• Chip clearing or part repositioning
• Short sensor faults
• Small feed or offset adjustments
• Quick operator interventions during an automatic cycle

These small events matter because they break flow and reduce effective runtime. In the language of overall equipment effectiveness, repeated small stops reduce availability and can also affect performance when cycles repeatedly slow down.

How to break utilization down by shift and operator group

The goal is not to create complex reporting for its own sake. The goal is to make daily losses visible in a way that leads to action. A simple structure works well for most small manufacturers.

Start with one bottleneck area

Choose one machine family or one constrained work center first. If you try to instrument the entire plant at once, definitions and discipline usually slip. Start where lost capacity hurts most: your bottleneck, most expensive asset, or most delay-prone cell.

Track by shift, crew, and machine

For each shift, capture:

• Scheduled production time
• Runtime
• Idle time
• Minor stop time
• Setup time
• Planned downtime if relevant
• Operator or crew assignment
• Primary work order or part family

Operator group matters because the same machine can perform differently depending on experience level, cross-training, and who handles setups or inspections. If multiple people share a machine, assign the record to the shift lead or the primary operator group for that period.

Use a basic comparison table

Even a weekly table can expose clear differences:

These numbers are illustrative, but the pattern is common. The key question is not “Why is utilization low?” The better question is “Why is second shift losing 5.5 more idle hours than first shift on the same asset?” That is specific enough to investigate.

What shift-to-shift differences usually reveal

High idle time on one shift usually points to support gaps

If one crew has materially more idle time than another, look first at process support, not operator effort. Common causes include:

• Material not staged before shift start
• Tool carts or consumables not replenished
• Delayed job packet release
• Long waits for QA signoff
• No maintenance or setup support on off-shifts
• Supervisors making frequent priority changes

This is why utilization should not be reviewed in isolation. If jobs arrive late to the machine, your queue discipline and WIP rules may be the real issue. Related reading: simple work-in-process limits by work center and material shortage tracking before a work order hits the machine.

High minor stops often indicate unstable standard work

When one crew has much more minor stop time, the causes are usually operational details that have never been standardized. For example:

• Different approaches to loading or clamping
• Inconsistent offset adjustment practices
• Different responses to recurring alarms
• Poor handoff notes between shifts
• Training gaps on a specific part family

Minor stops are where “the machine is running fine” can be misleading. A machine that restarts quickly after each short interruption may appear healthy while quietly losing dozens of minutes per shift.

Uneven setup burden can distort crew comparisons

Not every lower-utilization shift is underperforming. Sometimes one shift absorbs a disproportionate share of changeovers, first-article checks, or program prove-outs, while another shift gets longer continuous runs. That is why setup time should be shown beside runtime, idle time, and minor stops. If setup losses are large, pair this analysis with changeover time measurement by machine.

How to investigate the root cause without turning this into a blame exercise

Shift comparisons can become political if the review process is not disciplined. The point is to improve capacity, not rank people publicly.

Review differences with context

Look at the top three differences between crews over the last two to four weeks and ask:

1. Were they running comparable part mixes?
2. Did one shift inherit more setups or first-piece inspections?
3. Were staffing levels equivalent?
4. Did material availability differ by shift?
5. Were recurring alarms tied to one machine, one program, or one operator method?

Context matters because different part mixes create different stop patterns. A crew running short lots with high inspection frequency should not be judged against a crew running repeat parts with long cycle times.

Use short reason codes

Keep reason codes simple enough that operators will actually use them. For idle time, examples might include waiting on material, waiting on QA, waiting on forklift, no job released, operator break overlap, and staffing shortage. For minor stops, examples might include alarm reset, chip clear, offset tweak, sensor check, and part seating issue.

If your code list gets too long, data quality drops. If it is too vague, you cannot fix the problem. Aim for 8 to 12 practical reasons per category.

Verify with the people on the floor

After looking at the numbers, validate them with the crews. Ask operators what repeatedly interrupts flow on their shift. Often the data surfaces the pattern, and the crew explains the mechanism. That combination is much stronger than either one alone.

If a shift is losing capacity for the same reason three or four times a day, it is no longer a random interruption. It is a process problem.

Five actions that usually recover capacity fastest

1. Stage the first two hours of work before each shift starts

Many idle-time losses happen in the first hour of a shift while operators search for material, tooling, paperwork, or priorities. Build a simple pre-stage checklist so each machine starts with the next job ready to run.

2. Standardize the response to repeat minor stops

If recurring short interruptions are common, document the preferred operator response. A one-point lesson, setup photo, alarm response guide, or offset standard can reduce variation quickly.

3. Balance setup work across shifts

If one crew is doing most changeovers, utilization comparisons will be misleading and morale will suffer. Spread setup burden more evenly where practical, or at minimum separate setup time visibly in reporting so performance is interpreted fairly.

4. Match support coverage to the real loss pattern

If second shift loses time waiting for maintenance, QA, or material handling, the answer may not be more operators. It may be one floating support role during peak periods. This is a staffing decision informed by evidence rather than habit.

5. Escalate repeated queue and shortage issues upstream

If machines are idle because work is not ready, the root cause may be in planning, purchasing, or kitting. Use the data to trigger escalation earlier. For example, if a machine goes idle more than twice in a week due to missing material, that should create an upstream action item.

Simple metrics to review every week

You do not need a giant dashboard. For each constrained machine or cell, review:

• Utilization by shift
• Runtime hours by shift
• Idle hours by shift
• Minor stop minutes by shift
• Top three idle-time reasons
• Top three minor-stop reasons
• Setup hours by shift
• Output or completed quantity by shift

Use trends, not one-day snapshots. A single bad shift can be noise. A repeating weekly gap is a management problem worth solving.

If you want to estimate the financial impact of lost time, a simple model can help. FactoryOS offers a free downtime cost calculator and a free OEE calculator that can help frame the opportunity using your own assumptions.

Keep the measurement practical

The best utilization system is the one your shop will maintain. For most small manufacturers, that means:

• Clear time definitions
• A limited reason-code list
• Shift-level and crew-level comparisons
• Weekly review on bottleneck assets
• Action tracking tied to the biggest repeated losses

You do not need perfect data to find major capacity leaks. You need consistent enough data to see that one shift is losing far more idle time, that another is being overloaded with setups, or that repeated micro-stoppages are tied to a solvable method problem.

For broader guidance on improving manufacturing productivity and measurement systems, the National Institute of Standards and Technology is a credible reference point for small and midsize manufacturers.

Conclusion

Machine utilization by shift gives small shop owners a much sharper view of where capacity is actually being lost. When you separate runtime, idle time, and minor stops by crew, the conversation moves from opinion to evidence. You can see whether the issue is job readiness, uneven setup burden, weak handoffs, staffing gaps, or unstable standard work.

If you want to recover capacity without adding equipment, start measuring the difference between shifts on your most constrained machine this week. Then turn the biggest repeated losses into targeted fixes. If you are ready to make that visibility part of your daily operation, start a free FactoryOS trial.