● Edge · machine shop
Machining cells on one console.VMC, HMC, and CNC. Load, feed, and spindle.
eManage VMC / HMC / CNC Monitoring AI reads machining centres through the plant edge gateway. Run/stop, axis load, feedrate, spindle, and controller condition land on the live job card with a 72-hour store-and-forward buffer if WAN dies.
Loop
<50 ms
Cycle & idle
Cells
8–200
VMC, HMC, CNC
Buffer
72 h
WAN-down history
ERP
Job card
Cycle, tools, hours
eManage AI · CNC Monitoring
▾ Axis Load (CNC 1)
▾ Timeline
▾ Speeds
DEVICES · MAIN · DATA ITEMS
The problem
The controller already knows. The office still waits for the HMI.
Axis load is on the panel. Execution is in MTConnect. Tool and part counts sit in a separate CAM book. Payroll, OEE, and the job card argue because they never shared a clock.
Shift-end
Screenshot OEE
Supervisors type cycle hours after the pallet is already in inspection.
Split
Each OEM is an island
Fanuc, Siemens, and Haas screens never sit on the same shop-floor row.
Blind
WAN drop blanks the cell
Cloud-only MTConnect dashboards go dark the moment the fibre link drops.
How it works
Four moves.
One write-back.
01
Listen on the controller
MTConnect, FOCAS, and OPC UA from VMC, HMC, and CNC — including older serial frames that never had Ethernet.
02
Score on the edge
Run/stop, axis load, and micro-stops stay on the LAN. Relays still fire if the internet is dead.
03
Show the shop
Device tiles, axis-load gauges, execution timelines, and last-known values share one console — not three vendor HMIs.
04
Write the card
Cycle time, spindle hours, and part count post to the eManage job card. Piece-rate and OEE stop arguing.
The same numbers dispatch and payroll already use
Each centre is a machine in eManage. Program, part count, and spindle hours are not a second MES — they are the job card.
- VMC, HMC, and CNC mixed in one model — Fanuc, Siemens, Haas, local retrofits
- Axis load, feedrate, and controller condition on the same row
- 72-hour circular buffer so a fibre cut does not erase the shift
Questions plants actually ask
No. The controller stays. We read axis load, execution, and counters through the edge gateway and write the job card. Operators still start and stop the cycle from the machine.
Yes. Cells are machines in eManage. Axis set and rotary sit on the card; the device tiles and gauges do not care which OEM built the column.
The edge box keeps the loop. A 24–72 hour circular buffer holds run/stop and last-known values. On reconnect, alarms sync first, then history.
OEM screens stay on that brand. VMC / HMC / CNC Monitoring AI is the plant view: mixed centres, shop-floor ON/OFF, and payroll hours on the same eManage card.
Next
