How a rotor line, a traction-inverter line, an assembly line and a low-volume hypercar cell were unified into a single live namespace — and what a manufacturer can take away from it. The plant is simulated; the pipeline carrying its data is not.
A typical powertrain plant runs equipment from a dozen suppliers, each with its own controller, its own data format and its own island of visibility.
Station states live in PLCs. Quality measurements live in test-bench files. Downtime reasons live in an operator's head or a paper log. Answering a basic question — "what is my OEE right now, and which station is losing it?" — means stitching exports together days after the fact. By the time the answer arrives, the shift that caused it has gone home.
This reference plant was built to demonstrate the alternative: every station, every part and every event flowing through one open, queryable pipeline — visible seconds after it happens.
Each line, cell and test bench keeps its own records in its own format — nothing joins up across the plant.
KPIs assembled from end-of-shift exports describe yesterday's problems — too late to act on today's.
When a defect surfaces, tracing one serial back through stations, measurements and material lots takes days.
Open protocols at the edge, an MQTT unified namespace through a MonsterMQ broker, an indexed PostgreSQL time-series store — and live consoles reading from it in real time.
Open the live dashboard and watch the plant described above — or talk to us about applying the same architecture to a real one.