Everyone talks about UNS.
Here you can click one.

This is the plant's actual MQTT namespace — every topic the four lines publish, browsed read-only, straight off the broker's last-value store. Green dots are messages arriving now.

—topics

—active last 60 s

4production lines

5 srefresh

Topic tree

loading…

Select a topic

Pick any topic on the left — station states, measurements, transactions, orders, alerts. The payload you'll see is the same JSON any MES, historian or SCADA subscribed to this broker receives.

One namespace, every consumer

Lines publish once — rotor/M040/status, mes/alerts — and the dashboard, the historian and the AI assistant all subscribe to the same topics. No point-to-point integrations.

Structure is the contract

line / station / channel — status, measurements and transactions per station, plus mes/* for plant-level events. New consumers onboard by reading the tree, not the code.

Persisted as it flows

MonsterMQ archives every message into PostgreSQL — ~2.1M rows/day. This page reads the broker's last-value table; the analytics consoles read the archive.

Everyone talks about UNS.Here you can click one.

Topic tree

One namespace, every consumer

Structure is the contract

Persisted as it flows

Everyone talks about UNS.
Here you can click one.