F
factoryEdge AI MACHINE MONITOR

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.

By Ryan Lenhart · Updated

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.

Key takeaway

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:

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 typeHow it usually provides dataStatus for MTConnect-based software
Haas with Next Generation ControlHaas documents MTConnect on port 8082 with the model name in the pathDocumented by Haas; software version and network dependent
Mazak with a newer MAZATROL controlMazak's MTConnect FAQ describes machines as MTConnect-prepped, with adapters licensed and installed by Mazak serviceDocumented; needs adapter/agent
Mazak with legacy T-Plus, M-Plus, T32 or M32 controlMazak documents a third-party hardware adapter routeNeeds adapter/agent
Okuma with OSP-P controlOkuma offers a free MTConnect agent and adapter that needs THINC APIDocumented; config-dependent
FANUC 30i/31i/32i or 0iFANUC MTConnect Server is a separate PC product that reads the control over FOCASNeeds adapter/agent
Older control with no Ethernet dataThird-party hardware or I/O signalsNeeds adapter/agent
Any control "with MTConnect" on a brochureDepends on options installed at purchaseUnverified 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.

Compatibility note. MTConnect on a spec sheet does not prove a machine is connectable today. An agent has to be running and reachable from the monitoring PC. Some machines need an adapter, a controller option, a software update or dealer service first.

Step 2: Pick two pilot machines

Two machines is enough to learn, compare and build a habit. Choose:

  1. The bottleneck. The machine jobs queue behind. Every recovered hour there is shop-wide capacity.
  2. 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:

The Connect a CNC Machine checklist walks through each item in order.

Step 4: Run a 30-day pilot

WeekWhat to doWhat to look for
1Connect both machines, set ideal cycle times for the typical part, check that status matches what you see on the floorData accuracy: does "running" on screen match the spindle turning?
2Leave it alone. Look at the timeline each morning for five minutesGaps: long idle blocks, late starts, early finishes, short repeated stops
3Ask operators about the three biggest gaps. Add a short reason to eachCauses: waiting for material, programs, first-article inspection, tooling
4Change one thing and watch the timelineWhether 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:

  1. Was the data right? If status and part counts did not match reality, fix the connection before judging anything else.
  2. 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.
  3. 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:

PlanMachinesMonthlyAnnual
Free2$0$0
Shop5$99$990
Growth10$179$1,790
Scale25$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

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.

Important limitations. FEAI Machine Monitor reads accessible MTConnect data only. It does not connect over FOCAS, serial or proprietary protocols, and it does not claim universal CNC compatibility or specific productivity gains.

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.