An aerospace machining cell: seven CNC machines cutting structural parts across four work cells, 133 tags, over MTConnect.
The data is the machine's own MTConnect stream, so availability, execution state and the program running are reported the way a shop's own dashboards see them, with probing results alongside.
spindle load, speeds, feeds and temperatures per machine
execution state, program, tool number and part counts
probed feature measurements against the drawing
What it configures on Litmus Edge
On startup, and it removes exactly what it created when you are finished:
7 DeviceHub devices on the MTConnect driver, 133 tags
1 Digital Twin model serving all 7 machines
4 multi-input Analytics groups: tool wear risk, first part quality, thermal readiness, spindle utilisation
Scenarios you can inject
A dulling cutter raises cutting force until the unsupported web deflects and the part comes out thin, scrapping a forging worth more than the cycle that made it
A cold machine at the start of a shift under-travels and cuts oversize, which is the same measured feature moving the other way
A pallet pool running dry overnight leaves a spindle powered, available and earning nothing, which utilisation reported on state alone will not show
