CNC Production Monitoring
How many parts did each machine actually make, how long did each cycle take, and which job was running? CNC production monitoring answers those questions from the machine itself — no tally sheets.
Production numbers in most job shops come from one of two places: the operator's tally at the end of the shift or the ERP after someone reports the job. Both arrive late, both get rounded, and neither tells you *when* during the shift the parts were made — which is exactly what you need to see where time went.
CNC production monitoring reads production signals straight from the machine: part counts, cycle starts and stops, cycle duration, and the active program. The result is an hour-by-hour record of output that nobody had to write down.
Output totals tell you what happened. Output over time tells you why — the slow first hour, the gap after lunch, the cycle that drifted 15% slower on second shift.
What CNC production monitoring captures
| Signal | What it tells you | Typical MTConnect source |
|---|---|---|
| Part count | Parts completed, by hour, shift, and job | PartCount data item |
| Cycle start / end | When the machine was actually cutting | Execution state (ACTIVE, READY, STOPPED, INTERRUPTED…) |
| Cycle time | How long each part took vs its best cycle | Derived from execution state or count increments |
| Program | Which job or part was running | Program data item |
| Controller mode | Automatic, manual, or MDI | ControllerMode data item |
| Overrides | Feed or spindle overrides turned down | Override data items, where exposed |
What a specific machine reports depends on the control and how its MTConnect agent or adapter is configured. See What Data Does MTConnect Provide? for the full picture.
Part count monitoring — getting it right
Part count is the most valuable production signal and the easiest to get wrong.
- Confirm the control counts parts. Many controls increment a counter at program end (often triggered by M30 or a dedicated M-code). If the program never triggers it, the count stays flat.
- Handle multiple parts per cycle. A fixture with four parts per cycle should add four, not one. Set this in the program counter or account for it in reporting.
- Decide what counts as good. Machine count is total parts. Rejects and scrap usually have to be recorded separately for quality and OEE.
- Watch for resets. Operators sometimes reset counters at shift change. Monitoring should track increments over time, not just the current number.
- Validate against reality for a week. Compare monitored counts with the traveler or ERP for a few jobs before trusting the totals.
Cycle time monitoring — where hidden speed loss lives
Every program has a best proven cycle. Monitoring compares each actual cycle against it and shows when the machine runs slower than it can. Common causes of slow cycles:
- Feed override left at 80% after a prove-out
- Conservative programs that were never optimized for repeat work
- Tool wear forcing reduced feeds late in a tool's life
- Operator intervention mid-cycle (door opens, optional stops)
- Different programs or post versions on different machines for the same part
A 10% slower cycle on a job that runs 300 parts a week is a lot of spindle time. Cycle monitoring makes it visible within a shift instead of at month-end.
Production tracking by shift, machine, and job
Good production monitoring lets you slice output three ways:
- By shift — is second shift producing at the same rate as first on the same job?
- By machine — which machines produce the most good parts per scheduled hour?
- By job / program — which part numbers consistently run slower than their quoted rate?
That last view feeds back into quoting. If a part family always runs 20% over its estimate, either the estimate or the process needs to change.
Production monitoring vs downtime tracking vs OEE
They use the same machine data and answer different questions.
| View | Question |
|---|---|
| Production monitoring (this page) | What did we make, and how fast? |
| Downtime tracking | When were we not making parts, and why? |
| OEE | How much of planned time became good parts at full speed? |
FEAI Machine Monitor shows all three from one timeline per machine.
Real-time production visibility on the floor
A status board on a shop-floor screen changes behavior quickly. When everyone can see that a machine finished its last cycle 20 minutes ago, the gap gets closed faster. FEAI Machine Monitor's live view shows current state, current program, and recent output for every connected machine, and alerts can flag a machine that stops or idles longer than expected.
How FEAI Machine Monitor handles production data
- Reads production signals from supported machines through MTConnect, using read-only HTTP requests to the agent
- Stores production history locally on the Windows PC
- Shows part counts, cycles, and programs by machine and shift when the machine reports them
- Uses your ideal cycle time per machine for performance and OEE
- Exports reports for production meetings
- Ranks slow cycles and recurring loss as improvement opportunities with FEAI Intelligence on Growth plans and above
A simple rollout plan
- Connect your two busiest machines on the free plan.
- Verify part counts against travelers for one week.
- Set ideal cycles for the top repeat jobs.
- Review output by hour each morning. Look for the slow first hour and the gaps around breaks.
- Expand to the rest of the shop once the numbers are trusted.
Start free — 2 machines and see real output by hour within a day.
FAQ
What is CNC production monitoring?
It is the automatic collection of production data from CNC machines — part counts, cycle starts and ends, cycle times, active programs, and run state — so output by machine, job, and shift is recorded without manual tallies.
How do you track CNC part counts automatically?
Many controls expose a part count that increments at the end of each cycle, and MTConnect can publish it as a PartCount data item. Monitoring software reads that count over time. Some controls need part counting enabled in the program, for example with an M-code, before it reports reliably.
How do you monitor CNC cycle time?
By timing the machine's execution state from cycle start to cycle end, or from part count increments, and comparing it with the ideal or best proven cycle for that program.
What if my machine makes several parts per cycle?
Account for parts per cycle in your counting setup, either in the control's part counter or in how you interpret counts. Otherwise output and performance will be understated.
Is production monitoring the same as an MES?
No. Production monitoring records what machines produced. An MES also manages work orders, routings, labor, and quality records. Many shops start with monitoring.
Does FEAI track production for free?
Yes. Production history, part counts, and cycles are included on the Free plan for up to 2 machines when the machine reports them.