CNC Machine Monitoring for Small Shops
For job shops with a handful of machines and no dedicated IT team — how to find out which machines can be monitored, run a low-cost pilot on two of them, and decide from your own data whether to go further.
Large plants buy machine monitoring with project teams, IT departments and integration budgets. A small job shop has an owner, a lead machinist and a list of jobs due Friday. This guide is for the second group: shops with roughly 2 to 20 CNC machines who want to know whether monitoring is worth it without a long contract or a consultant.
The approach is simple. Find out which machines can provide data, connect two of them, watch them for a month, and let the data decide what happens next.
In a small shop, the goal of monitoring is not a dashboard on a TV. It is one better decision a week: which job to move, which setup to fix, which machine to staff first.
Is monitoring worth it for a small shop?
Monitoring pays attention to time. It shows when each machine was cutting, idle, stopped or in alarm. That matters most when:
- One or two machines limit what the shop can ship, and nobody is sure how many hours they actually cut.
- Second shift or lights-out runs happen without anyone watching.
- Quotes are based on cycle times that nobody has checked against reality.
- The owner spends evenings asking "what happened on the Mazak today?"
It matters less when machines are fully staffed, work is steady and the owner is on the floor all day. In that case paper notes may already tell you enough. Be honest about which shop you are before you spend time on setup.
Step 1: Inventory your controls
Before choosing software, list every machine, its control and how it might connect. This takes an hour and saves weeks.
| Machine type | How it usually provides data | Status for MTConnect-based software |
|---|---|---|
| Haas with Next Generation Control | Haas documents MTConnect on port 8082 with the model name in the path | Documented by Haas; software version and network dependent |
| Mazak with a newer MAZATROL control | Mazak's MTConnect FAQ describes machines as MTConnect-prepped, with adapters licensed and installed by Mazak service | Documented; needs adapter/agent |
| Mazak with legacy T-Plus, M-Plus, T32 or M32 control | Mazak documents a third-party hardware adapter route | Needs adapter/agent |
| Okuma with OSP-P control | Okuma offers a free MTConnect agent and adapter that needs THINC API | Documented; config-dependent |
| FANUC 30i/31i/32i or 0i | FANUC MTConnect Server is a separate PC product that reads the control over FOCAS | Needs adapter/agent |
| Older control with no Ethernet data | Third-party hardware or I/O signals | Needs adapter/agent |
| Any control "with MTConnect" on a brochure | Depends on options installed at purchase | Unverified until tested |
For each row, check whether an MTConnect agent is already answering. The quickest test is in How to Test an MTConnect Connection. Brand-specific notes are on the Haas, Mazak, Okuma and FANUC pages.
Step 2: Pick two pilot machines
Two machines is enough to learn, compare and build a habit. Choose:
- The bottleneck. The machine jobs queue behind. Every recovered hour there is shop-wide capacity.
- A machine that connects easily. A newer control with MTConnect already running. Prove the process works before tackling the difficult ones.
If the bottleneck is hard to connect, start with two easy machines and add it later. A pilot that stalls on connection problems teaches nothing about production.
Step 3: Get the basics in place
You do not need a server room. You need:
- A Windows PC on the shop network that stays on during production. FEAI Machine Monitor is a 64-bit Windows desktop app that installs per user.
- Ethernet to each pilot machine. Wi-Fi bridges work in some shops, but a cable removes one variable.
- Each machine's IP address, set as a fixed address or reserved in the router so it does not change.
- A browser test. From the PC, open the agent's
/currentURL. If XML appears, the software can read it.
The Connect a CNC Machine checklist walks through each item in order.
Step 4: Run a 30-day pilot
| Week | What to do | What to look for |
|---|---|---|
| 1 | Connect both machines, set ideal cycle times for the typical part, check that status matches what you see on the floor | Data accuracy: does "running" on screen match the spindle turning? |
| 2 | Leave it alone. Look at the timeline each morning for five minutes | Gaps: long idle blocks, late starts, early finishes, short repeated stops |
| 3 | Ask operators about the three biggest gaps. Add a short reason to each | Causes: waiting for material, programs, first-article inspection, tooling |
| 4 | Change one thing and watch the timeline | Whether the change shows up in run time |
Keep a one-page log of what you changed and when. That is what turns a monitoring pilot into a decision.
Step 5: Decide
At the end of the pilot, answer three questions:
- Was the data right? If status and part counts did not match reality, fix the connection before judging anything else.
- Did it change a decision? One moved job, one fixed setup or one changed shift start is evidence. A nice dashboard nobody opened is not.
- Which machines are next? Add the machines where a decision is most likely, not simply the next ones on the list.
If the answer to the second question is no, monitoring may not be a priority yet. That is a valid result and it cost you very little to learn.
What it costs a small shop
With FEAI Machine Monitor the pilot itself is free for two machines. The real costs are the PC, cabling, and any adapter or controller option a machine needs. If you expand:
| Plan | Machines | Monthly | Annual |
|---|---|---|---|
| Free | 2 | $0 | $0 |
| Shop | 5 | $99 | $990 |
| Growth | 10 | $179 | $1,790 |
| Scale | 25 | $399 | $3,990 |
Other vendors publish different models, from per-machine monthly pricing to perpetual licenses with hardware. Some do not publish prices at all. See How Much Does CNC Machine Monitoring Cost? and the free options comparison before you decide.
Mistakes small shops make
- Connecting every machine first. Setup drags on and nobody looks at the data. Start with two.
- Skipping the ideal cycle time. Without it, performance and OEE are meaningless. Set one per typical part.
- Treating idle as failure. A machine waiting for a first-article check is idle for a reason. Find the reason before blaming the operator.
- Using the screen as a surveillance tool. Operators who feel watched stop helping. Share the timeline with them and ask what they see.
- Buying for the dream shop. Choose software for the machines you have now, and check the price of the next tier before you start.
A note on people
In a small shop everyone knows everyone. Tell the team why you are monitoring before the first machine goes live: to find waiting time, not to count bathroom breaks. Show them the timeline in week one. The best explanations of a stop come from the person who was standing next to the machine.
Start the pilot
If at least one machine already answers an MTConnect /current request, you can start today: Start Free — Monitor 2 Machines. If not, work through Already Have MTConnect? to find out what each machine needs.
FAQ
Is machine monitoring worth it for a shop with only a few machines?
It can be, if a machine's hours limit what you can ship. With few machines each idle hour matters more. The way to find out is a short pilot on your busiest machine, not a shop-wide rollout.
Do I need an IT department?
No, but you need someone who can find a machine's IP address, plug in an Ethernet cable and check that a PC can reach the machine. Haas, Mazak, Okuma and FANUC setups each have their own steps, and some need the dealer.
What if my machines are old?
Older controls often have no network data. They may need a third-party hardware adapter or an MTConnect adapter before any MTConnect-based software can read them. Start the pilot on a newer machine.
How long should a pilot run?
Plan on about 30 days: one week to connect and check data, then three or more weeks of normal production before you judge the results.
What does it cost to start?
FEAI Machine Monitor is free for 2 machines. Your costs are a Windows PC on the shop network, any network cabling, and any adapter or controller option a machine needs. Paid plans start at $99 per month for 5 machines.