Production tracking
Part counts from the controller, not the clipboard
ThingConnect reads production counts and cycle data straight from each CNC control, so you see actual output against plan, hour by hour, while the shift is still running.
The gap between the plan and the floor
- Actual output is discovered at shift end — 8 hours too late to recover the shortfall.
- Hourly boards are filled in by hand, when someone remembers, in someone’s handwriting.
- Cycle times drift 10% over months and nobody notices until delivery dates slip.
- Production reports take an hour of Excel every morning.
How ThingConnect does it
Counts with zero data entry
Part counts come from the controller’s own registers. No tally sheets, no end-of-shift reconstruction.
Hour-by-hour vs plan
The classic lean hour board, digital and automatic — every hour’s output against target, gaps visible while they’re still recoverable.
Shift reports that write themselves
Output, downtime, and OEE per machine and line, ready at shift end — exportable to Excel, because we know where reports actually go.
Common questions
Where do part counts come from?
From the CNC controller’s part-count data, read over the native connection. Where a control doesn’t maintain counts, cycle completions are counted from state data.
Can it track against a production plan?
Yes — enter the job and target quantity, and the dashboard shows progress and projected completion at the current pace. Full scheduling systems are deliberately out of scope; we track against the plan you already have.
Does it work for job shops with changing parts?
Yes. Job and part context can be set from the operator station, and cycle-time references adjust per part program.
Can reports be exported?
Every report exports to Excel. Shift summaries can also be sent automatically at shift end.
See it on machines like yours
A 30-minute demo, then a pilot on your own floor if it fits.