Talk to the equipment you already own.

The problem

"Digital transformation" too often means rip-and-replace. Vendors quote six-figure upgrades to put a modern dashboard on equipment that's been working fine for fifteen years. The IT/OT integration project becomes the project, and the actual operational outcome you wanted is never delivered.

How WaterTwin solves it

• MQTT-native. EMQX broker built in. Per-device usernames, TLS, ACLs — provisioned automatically when you add a device. No shared credentials, no cleartext brokers.
• OPC UA bridge. Pull tags from any OPC UA server (PLCs, SCADA gateways, energy-management systems) into the live twin.
• Modbus TCP poller and bridge. Poll Modbus devices on a configurable schedule, or bridge them directly into the telemetry stream.
• Sparkplug B first-class. Existing Sparkplug devices and brokers work without translation. Edge nodes register and report on connect.
• Weather data feeds. Automatic OpenWeatherMap ingestion so rules can correlate weather with network behaviour.
• REST API + SignalR. Every read and write is also available to your control system, BI tool, or in-house integration.

How it works

1. Pick the protocol your equipment speaks.
2. Configure the bridge (usually a short YAML or a UI form).
3. Telemetry flows into the same platform as everything else. No translation layer for users.

Why this matters for your business case

• The CFO sees the existing-equipment investment preserved.
• The ops team sees their familiar tags, in a modern interface.
• The IT team sees a documented integration pattern instead of a custom project.