R&D · Project 01 · In development

CNC machine monitoring: know why every machine stopped

We are developing a CNC machine monitoring system that reads each machine control and shows the whole shop: what is running, what has stopped, the condition reported by the control and the reason the operator gives.

Illustration: a machining centre in alarm, the condition reported by its control, an operator tablet asking why it stopped and the shift timeline. Example data.
Illustration · example data

What CNC machine monitoring tells you

Machine monitoring takes its data straight from each machine control, so you see how the machines are really used rather than estimates on a whiteboard. For a machine shop it answers four questions.

We are building it for UK machine shops with mixed fleets: Haas, Okuma, Mazak and Hurco machines first, with Fanuc controls and older machines to follow.

What works today, and what is in development

We only mark something as working once we have tested it.

Status at October 2026
CapabilityStatusDetail
Reading MTConnect controlsWorkingCollector tested against MTConnect reference agents (Okuma and Mazak devices) and our CNC emulator. Not yet installed on a customer machine.
Read-only, outbound-only collectorWorkingTested in our lab.
Machine states and utilisationWorkingUtilisation engine tested on our test rig: it reproduced 110 state changes in 5 minutes exactly, and ran against our CNC emulator with no false offline periods.
Fleet, machine detail and downtime screensWorkingTested in our lab against live emulator data, through the same secure web front end a pilot site would use. Not yet at a customer site.
OEE (availability, performance, quality)In developmentCalculated on our test rig, including rejects recorded on the operator tablet. We will check its accuracy against a manual time study before using it at a customer.
Operator reasons for each stop, on a tabletWorkingTested in our lab: the tablet asks why a machine stopped after two minutes, keeps working through network drops, and is paired to its machine with a code. Not yet at a customer site.
Shop-floor TV and shift reportsIn developmentDesigned; both are shown below as design previews.
Fanuc controlsIn developmentAdapter in development.
Older and manual machinesIn developmentCurrent sensor in development. Fitting it is electrical work inside the machine cabinet, carried out by a competent person and agreed with you.
Siemens and Heidenhain controlsPlannedNot supported yet.

The screens we are designing

These are design previews of the machine monitoring software, with example data, not the running product.

Design preview of the CNC machine monitoring fleet view: machine states, utilisation, parts and shift timelines. Example data.
Every machine at a glance. Live state, utilisation against target and the shift timeline for the whole shop, with problems sorted first.Design preview · example data
Design preview of the shop-floor TV with one tile per machine. Example data.
A screen for the shop floor. Any machine that is not running fills its tile, so the right person sees it from across the shop.Design preview · example data
Design preview of CNC downtime tracking by reason and by machine. Example data.
Where the hours went. Downtime by reason and by machine, with stops still needing a reason highlighted.Design preview · example data
Design preview of machine detail with OEE split into availability, performance and quality. Example data.
Availability, performance, quality. OEE split into its three parts for one machine, with planned breaks left out.Design preview · example data
Design preview of the operator tablet in alarm, asking why the machine stopped. Example data.
Why it stopped. The condition reported by the control, and a tablet at the machine so the operator can record a reason.Design preview · example data
Design preview of the phone view listing machines that need attention. Example data.
On your phone. The machines that need attention first, wherever you are on site.Design preview · example data
Design preview of the end-of-shift report: utilisation, OEE, downtime by reason and a table by machine. Example data.
The shift report. Utilisation, OEE, the top downtime reasons and every machine, at the end of each shift.Design preview · example data

Read-only, outbound only

Illustration: MTConnect controls linked to a read-only collector, which sends data outbound to BSE’s service in the EU. Fanuc adapter and current sensor shown as in development.
Illustration · example data

Which machines it can read

ControlRouteStatus
Haas NGC (2017 and later)MTConnect, built into the controlNot yet tested
Okuma OSP-P300 / P500MTConnect, Okuma's MTConnect appWorking
Mazak Smooth / Smart / PreviewMTConnect, licence file per machine from MazakWorking
Hurco WinMaxMTConnect, built in on current softwareNot yet tested
Fanuc 0i / 30i seriesAdapterIn development
Older and manual machinesCurrent sensor in the cabinetIn development
Siemens 840D sl, Heidenhain TNCTo be decidedPlanned

"Working" means our collector has read the standard MTConnect data these controls publish, using reference agents. "Not yet tested" means the control publishes the same standard, but we have not yet read one. We have not yet installed the collector on a customer's machine.

Work with us as a pilot partner

We are looking for UK machine shops to help us develop and test this. Email us the make, model and control of your machines, and we will come back to you.

Email
enquiries@bse-eng.co.uk
Phone
0330 341 2424

CNC machine monitoring: common questions

What is CNC machine monitoring?

Software and a small piece of hardware that read data from a CNC machine control, such as its state, alarms, program and part count, and turn it into live machine status, utilisation and downtime figures for the whole shop.

Which CNC controls can it read?

Controls that publish MTConnect data. We have read Okuma and Mazak controls through MTConnect reference agents; Haas NGC and Hurco WinMax publish the same standard and are next to test. A Fanuc adapter and a current sensor for older or manual machines are in development. Siemens and Heidenhain controls are planned.

Can it change anything on our machines?

No. The collector only reads from the control. It cannot change a program, an offset or a setting.

Do we need to open ports in our firewall?

No. The collector sends data outbound over HTTPS only. No ports are opened into your network.

Does it calculate OEE?

Yes, on our test rig. Availability and performance come from the control, and quality from rejects recorded on the operator tablet. We will check its accuracy against a manual time study before using it at a customer.

Where is the data held?

In an EU data centre in Germany. Your data is yours, and you can have a copy of all of it.

Can we buy it now?

Not yet. This is an R&D project in development. We are looking for UK machine shops to work with us as pilot partners, so register interest if you would like to be one.

From machine data to shop-floor decisions.