Telemetry
SCADA integration
One-way and read-only. Today the district-side agent reads the Ignition tag historian. Adapters for the other systems municipal water districts run (AVEVA Wonderware and PI, Rockwell FactoryTalk, Trihedral VTScada and GE Vernova iFIX) have been rebuilt and pass their tests against simulators of each vendor’s documented interface (62 tests, 12 October 2026); each is marked available here only after a verified read of a district’s own system in a pilot.
SCADA integration
It reads your tags. It never touches your plant.
An annual pump test is one photograph of a moving thing. The tags you already historize — flow, discharge pressure, water level, motor kilowatts, drive speed and vibration — turn that photograph into a film, without adding a single sensor.
One-way, outbound, read-only. No exceptions. A small agent runs inside your perimeter and pushes out. Waterwell IQ never opens a connection into your control network and never writes a value to a tag. Water sector guidance requires operational technology connections to be denied by default, so we designed for that first rather than retrofitting it after your risk and resilience assessment asks.
Ignition today. The rest as each is proven.
The agent reads the Ignition tag historian through a resource on your gateway, read-only and outbound only. Adapters for AVEVA (Wonderware and PI), Rockwell FactoryTalk, VTScada and GE iFIX are in testing; each is listed as available only after a verified read of a real district system. Map tags to roles once.
One signed contract for every source
Every reading arrives the same way: a signed HTTPS envelope, sent outward, with units and quality on each sample. An integrator can post to it from any system that can make a signed HTTPS request; a packaged OPC UA adapter is in testing, and generic historian-database and scheduled-CSV adapters are planned.
Efficiency weighted by real runtime
With continuous data the platform weights efficiency across the load points your pump actually runs at, instead of the one point a test truck happened to catch. A test truck cannot do that.
Telemetry is outbound-only and read-only: an agent inside the district network posts historian samples out over TLS. There is no inbound path.
| Tag role | Units | Interval | What it unlocks |
|---|---|---|---|
| flow | gpm | 1–15 min | Operating point, production totals, region of operation |
| discharge_pressure | psi | 1–15 min | Total dynamic head with the water level |
| water_level | ft bgs | 15–60 min | Drawdown, specific capacity, the static-lift correction |
| motor_kw | kW | 1–15 min | Wire-to-water efficiency and energy intensity |
| run_state | bool | on change | Stored today; run hours and start counts for the life model are on the roadmap |
| vfd_hz | Hz | 1–15 min | Speed normalization so trends compare like with like |
| vibration | in/s rms | 1–60 min | Condition against the limit for the current operating region |
Compatibility
Ignition today. The rest as each is proven.
There is one telemetry contract: a signed, outbound JSON envelope of historian samples, produced by an agent inside your network. Today its Ignition adapter is built; the rows marked In testing pass their tests against each vendor’s documented interface and wait for a real system. Whichever source your district uses is verified against your own system during the pilot, on your network, by your integrator.
| SCADA / historian | How it connects | Status? |
|---|---|---|
| Inductive Automation Ignition | Native tag-historian adapter (gateway Web Dev resource) | Available: history as far back as the agent is set to read |
| AVEVA PI (OSIsoft PI System) | PI Web API (read of recorded values, paged) | In testing: passes its simulator tests; available after a verified read of a district system |
| AVEVA / Wonderware Historian, System Platform, InTouch | Read-only SQL against the Historian’s Runtime database (Delta retrieval); OPC UA where enabled | In testing: passes its simulator tests; available after a verified read of a district system |
| Rockwell FactoryTalk View SE / FactoryTalk Historian | FactoryTalk Historian WebAPI (Historian SE 12.x); PI Web API on earlier releases; OPC UA where enabled | In testing: passes its simulator tests; available after a verified read of a district system |
| GE Vernova iFIX / CIMPLICITY / Proficy Historian | Proficy Historian REST API; OPC UA where enabled | In testing: passes its simulator tests; available after a verified read of a district system |
| Siemens WinCC / WinCC OA | OPC UA, Connectivity Pack (SQL), scheduled export | Planned |
| Trihedral VTScada | VTScada REST SQLQuery against the History table; OPC UA where enabled | In testing: passes its simulator tests; available after a verified read of a district system |
| Schneider / AVEVA Geo SCADA (ClearSCADA), Survalent, Ovarro, Emerson | OPC UA, scheduled export, or the vendor’s SQL/ODBC interface | Planned |
| Cloud loggers and remote-monitoring services — XiO, Mission, Ayyeka, In-Situ HydroVu, Trimble Unity, Sensaphone | REST adapter against the vendor API, or the export they email | Planned |
| A PLC or RTU with no historian at all — Allen-Bradley, Siemens, Modicon, Opto 22, Red Lion | Modbus TCP polling, OPC UA (via Kepware/KEPServerEX or the PLC’s own server), or MQTT from the PLC | Planned |
| A spreadsheet on the first of the month | Drop it in a folder; a scheduled-CSV adapter would read it | Planned |
One contract. Ignition today; OPC UA in testing; four planned
Ignition
Point the adapter at your well tag folders on the gateway. Tag security is respected because the gateway runs the history query itself.
OPC UA (in testing)
Historical access (HistoryRead) where the server has it, with continuation points. Sign-and-encrypt as your server requires; a user that can read history and nothing else.
MQTT (planned)
Would subscribe to plain JSON or Sparkplug B from a broker inside your network and publish nothing back. Not built yet.
Modbus TCP (planned)
Would poll registers from the PLC on the interval you set, with scaling and deadbands, for districts with no historian. Not built yet.
Read-only SQL (planned)
Would run one SELECT template against any historian database — Postgres, SQL Server or MySQL — with a login that can do nothing else. Not built yet; the AVEVA Historian adapter above is the SQL Server case.
REST / JSON (today, by your integrator)
Any system that can make a signed HTTPS request can post samples to the contract today — a script your IT already runs, or a cloud logger’s export. A packaged generic REST adapter is planned.
CSV export (planned)
Every historian can schedule an export to a folder; an adapter that watches the folder and reads long or wide layouts, any timestamp format, any time zone, is planned. Not built yet.
Deployment
What your integrator actually has to do
| Step | Who | Effort |
|---|---|---|
| Grant the agent read-only access to your historian (for Ignition, a Web Dev resource on the gateway) | Your integrator | About an hour |
| Issue an agent key in Waterwell IQ (Settings → Telemetry); it is shown once and stored only as a hash | Your district owner | Minutes |
| Run the agent on a small host on the historian VLAN; it makes one outbound HTTPS connection and listens on nothing | Your IT or us | Half a day |
| Map tag paths to roles in one JSON file | Your integrator | About an hour for a fleet |
| Backfill history from the day your historian started | Automatic | Unattended |
Ask us for the integrator questionnaire. It is two pages, it tells you exactly what we need, and it is written so your integrator can answer it without a call.
What we will never ask for
An inbound firewall rule. A VPN into your control network. Write access to any tag. A credential that could reach the plant. If a vendor’s integration plan needs any of those, it is not ours.
If you can only add one instrument
Make it a water level transducer or a sounding tube sensor. Efficiency alone will trend, but without water level the platform cannot separate pump wear from screen fouling from aquifer decline — and that separation is the whole point.