F
factoryEdge AI MACHINE MONITOR

CNC Downtime Tracking

Downtime is rarely one big breakdown. It is dozens of short stops and long waits that never make it onto a log. Here is how to measure them, put a price on them, and get the hours back.

By Ryan Lenhart · Updated

CNC downtime cost calculator

Estimate what unplanned stops and idle waiting cost across your machines. Runs entirely in your browser.

Lost hours per week–
Cost per week–
Cost per year (50 weeks)–

Ask a shop floor how much downtime they had yesterday and you will hear about the alarm on machine 4 and the broken tool on the lathe. Ask the machines and you get a different answer: a dozen gaps between cycles, a 40-minute wait for a first-article sign-off, a program that was not ready at shift change, and an hour where the operator was running two other machines.

That second answer is the one worth acting on. CNC downtime tracking means capturing every stop during planned production, classifying the big ones, and reviewing them often enough to fix the causes that repeat.

Key takeaway

Breakdowns are loud and get fixed. Waiting is quiet and gets accepted. On most machine timelines, waiting is the bigger loss.

The three kinds of stop — keep them separate

TypeMachine conditionTypical causesWho fixes it
Unplanned downCannot runAlarms, crashes, broken tools, hydraulic or spindle faultsMaintenance, operators
Idle / waitingHealthy, not cyclingMaterial, tools, programs, inspection, operator coverage, forkliftScheduling, supervisors, programming, quality
Planned stopStopped on purposeScheduled maintenance, planned setups, meetingsPlanning

When these are lumped into one "downtime" number, maintenance gets blamed for scheduling problems and nobody owns the waiting. Separating them is the single most useful thing a downtime system does.

The causes behind most CNC downtime

From the timelines of typical job shops, the recurring losses look like this:

  1. Waiting on material or fixtures — the job is released but the stock or fixture is not at the machine.
  2. Waiting on programs or prove-outs — the next job's program is not posted, or needs edits at the control.
  3. Setups and changeovers — especially the parts of setup that could happen while the previous job is still running.
  4. First-article and in-process inspection — the machine sits while the part walks to the inspection room and back.
  5. Operator coverage — one person running three machines means two of them wait.
  6. Tool problems — tools not preset, not in the crib, or breaking early.
  7. Alarms and faults — real, but usually fewer minutes than all the waits combined.
  8. Shift change and breaks — machines that stop for 20–40 minutes around every shift boundary.

None of these show up as one big event. They show up as minutes, many times a day, on many machines.

Why manual downtime logs miss most of it

Paper logs and end-of-shift spreadsheets capture the stops people remember. In practice, short stops — under about 10–15 minutes — are routinely missed or rounded away, and stop times get written from memory hours later. The result is a log that undercounts downtime and over-represents the dramatic events.

Manual logAutomatic tracking
Short stopsUsually missedEvery state change recorded
Start and stop timesEstimated laterTimestamped by the machine
Operator effortEvery stopOnly a reason on significant stops
Idle vs downInconsistentSeparated by machine state
Trend analysisManual compilationBuilt in

Manual input still matters for one thing: why. The machine knows it stopped. The operator knows it was waiting for the inspector. The best systems combine automatic timing with a light human reason code.

How to track CNC downtime — step by step

Step 1: Define planned production time

Write down which machines are expected to run on which shifts. Downtime only means something against a plan.

Step 2: Capture machine state automatically

Use monitoring software that reads running, idle, stopped, and alarm states from the machine. FEAI Machine Monitor does this through MTConnect on supported machines and builds a minute-by-minute timeline.

Step 3: Set a short reason code list

Start with something like:

Add a code only when it would change a decision.

Step 4: Code the big stops, not every stop

Ask operators to explain stops longer than a threshold — say 10 minutes. The timeline already has the rest.

Step 5: Review daily, act weekly

A ten-minute morning review of yesterday's longest stops, with one owner per stop, does more than a monthly downtime report nobody reads.

Step 6: Verify the fix

After a change, compare the same machine on the same shifts. If the stop category did not shrink, the fix did not work.

How to reduce CNC downtime once you can see it

LossPractical countermeasures
Waiting on materialKit jobs the shift before. Stage material at the machine before the current job ends.
Waiting on programsPost and prove programs ahead of release. Track program-ready status on the schedule.
Long setupsSeparate internal and external setup work. Preset tools. Standardize fixtures and zero points.
Inspection waitsBring first-article checks closer to the machine. Prioritize the inspection queue by bottleneck machines.
Operator coverageUse the timeline to rebalance machine assignments. Stagger cycle ends across attended machines.
Shift-change gapsOverlap handoffs. Leave the next job staged and the machine running at shift end.
Repeat alarmsRank alarms by total minutes. Fix the top three root causes rather than resetting them.

Start with the bottleneck machine. An hour saved there is an hour for the whole shop. An hour saved on a machine that waits for work anyway changes nothing. See Find CNC Bottlenecks for how to identify it.

Downtime and OEE

Downtime is the availability part of OEE. If a machine planned for 480 minutes stops for 96, availability is 80% before speed or quality losses are counted. Reducing downtime is usually the fastest way to raise OEE in a job shop. Try the numbers in the OEE calculator.

Tracking downtime with FEAI Machine Monitor

FEAI Machine Monitor records machine state through MTConnect on supported CNC machines and gives you:

Compatibility note. Downtime tracking from machine data requires machines that provide accessible MTConnect data through an MTConnect Agent or compatible endpoint. The quality of state detection depends on which data items the control exposes. Some machines need an adapter or configuration first.
Important limitations. Tracking shows where time goes. It does not reduce downtime on its own — your countermeasures do. Results vary by shop.

Start tracking downtime today

Connect your bottleneck machine and one more, free, and look at a full week of real stops. Start free — 2 machines.

FAQ

What is CNC downtime?

CNC downtime is time during planned production when a machine is not making parts. It includes breakdowns and alarms, but in most shops the larger share is idle waiting for material, programs, tools, inspection, or an operator.

What is the difference between idle time and downtime?

Idle means the machine is healthy but not cycling, usually because it is waiting on something. Down means it cannot run because of a fault, alarm, or maintenance. Separate them because different teams fix them.

How do you track CNC downtime automatically?

Monitoring software reads machine state from the control, for example through MTConnect, and records every transition between running, idle, stopped, and alarm. Operators then add a short reason to the significant stops.

What are the most common causes of CNC downtime?

Waiting for material, tools, programs, first-article approval, or an operator, followed by setups and changeovers, alarms and crashes, and maintenance. Waiting usually costs more than breakdowns.

How many reason codes should we use?

Start with five to eight. Too many codes lead to random choices. Add a code only when it would change a decision.

How much does CNC downtime cost?

Multiply lost spindle hours by what an hour of that machine is worth to you. Use the calculator on this page with your own numbers.