See the plant live, and change the maths yourself
DynamicPlantMesh connects the equipment you already have over OPC-UA, OPC classic DA and MQTT v5, and puts what it sees in a browser: live dashboards, trends, gauges and event timelines that update as the plant runs. Nothing on the plant floor is replaced, and the historian it records into ships with the platform.
The part that matters for a small engineering team is the second half of that sentence. KPIs, alarm logic and calculated traces are expressions written in the app, with more than 40 plant functions for historian aggregates, state durations, signal maths and bit decoding. Changing how utilisation is calculated is an edit, not a software release.
What your engineers get
- Trend statistics, not just lines. 19 statistics per trace, including the time at which every minimum and maximum occurred, generated from the window on screen instead of an export to a spreadsheet.
- Event and downtime intelligence. How long, how often, what it looked like last time, and what the process was doing while it happened, with one click from the event to the trend behind it.
- Long, fine-grained history. Per-second to per-day resolution over any historical range, so "show me this pump's vibration during the same shift last quarter" is a trend, not a ticket.
- Answers in plain language. Two in-app assistants, powered by DBS Invenio, answer from the live historian, and 18 MCP tools give agents you run yourself governed access to equipment, events, KPIs and time-series. It stays off until you enable and configure it.
- Exports that survive the meeting. Resampled data to Excel, event grids to Excel or PDF, and charts as 2560×1440 PNGs.
How it is put together
The platform installs on Windows hosts you already manage, as six cooperating services around an embedded MQTT v5 broker and its own historian backend on a relational database. A field gateway service connects the OPC-UA and OPC classic DA equipment, buffers to disk while the broker is unreachable and replays on reconnect, so an outage becomes a delay bounded by the disk buffer you configure.
Each service restarts and scales on its own, which is why a heavy KPI recalculation never slows the web app down. There is no container orchestration team in that list, deliberately. Sign-in is native or Microsoft Entra ID, and integration is over governed REST APIs.
Who it is for
Plant and production managers watching KPIs against targets and downtime across equipment and shifts. Process and reliability engineers doing root-cause work with trends, event comparison and calculated traces. Control-room teams who need equipment status and alarms with SMS and email notification. IT and OT integrators who have to connect it all to something else.
Where it fits
DynamicPlantMesh is the plant-analytics layer, and the historian stays the system of record. The in-app assistants run on DBS Invenio, our own AI harness, which is also what we build on when an application needs to sit on top of that data and reach people who never open the plant system. We also run plant-analytics projects as a service, whether or not the historian underneath is ours.
Find out more
The full product site, with the platform, AI, connectivity, architecture and security detail, is at dynamicplantmesh.com. For pricing, tell us what you run — equipment, protocols and a rough tag count — and we will reply within one working day.