Seven CNC machines in four cells over MTConnect, where a dulling cutter scraps a titanium forging worth more than the cycle that cut it.
A machine shop cutting aerospace structures: seven CNC machines in four cells, 133 tags, over MTConnect. Four scenarios run at once, one per cell, each with a healthy machine beside it so the comparison is on screen rather than remembered.
A dulling cutter scraps a forging worth more than the cycle that cut it. Flank wear raises cutting force, the unsupported web deflects and springs back, and more material comes off than the program asked for, while the tool life counter still shows parts remaining. A cold ballscrew is short, so the axis under-travels and the first parts of a shift come out thick; it corrects itself as the machine warms, which is exactly why it is expensive. Carbide changed on a fixed part count throws away most of every edge. And a spindle whose pallet pool has run dry stays powered, stays AVAILABLE, and simply stops being ACTIVE, so every dashboard watching availability reports it as fine.
The tag names are not invented. EXECUTION, SPINDLE_SPEED, PATH_FEEDRATE, LOAD, PART_COUNT and TOOL_NUMBER are DataItem types defined by MTConnect Part 2, so Litmus Edge browses the agent and discovers the shop rather than being told about it, and every reading on the operator view carries the DataItem name it arrived as.
The solution configures Litmus Edge itself on startup: seven DeviceHub devices, one MachineTool Digital Twin model with seven instances, and four Analytics groups. It removes exactly what it created.
