You may not need a SCADA deployment to know a well is down
SCADA is not the wrong answer. It is the right answer to a different question: controlling a facility in real time, safely, at scale. If that is your question, buy it.
Knowing whether a well is down, what the pressure has been doing, and who to call when it changes is a different question. Answering it does not require running a historian and a host.
Keep the SCADA. We feed it.
This is the part worth reading before the table. If you already run SCADA, nothing here asks you to replace it, and we would argue against replacing it. We publish to it.
A Sphynx publishes every value over MQTT on a documented topic per channel, so a host can subscribe to exactly what it needs. For VTScada there is a connector with prebuilt tag types, so the integration is configuration rather than a project. Your host keeps doing control; Field Warden covers the sites that were never going to be worth a full deployment, and puts them in the same asset tree as the ones that were.
Capability by capability
| Capability | Full SCADA | Field Warden |
|---|---|---|
| Real time control at scale | What it is for, and nothing here replaces it. Deterministic, local, and proven over decades. | Setpoint writes with range enforcement. Not a control system, and not sold as one. |
| Safety and interlocks | Belongs here, with the PLC. Rated, auditable, and independent of a network. | Nothing. An interlock that has to hold in milliseconds without a network is a PLC. |
| What it takes to run | A host, a historian, licences, a server somebody patches, and usually an integrator on retainer. That is a real cost and often the right one. | A device and a browser. Nothing to host, nothing to patch, no server to own. |
| Time to first reading | Weeks to months, because the host and the tag database come first. | A device arrives configured. Reading in an afternoon. |
| Remote access | Often a VPN, a jump host, or a thin client, and frequently the thing that is awkward on a phone at 3am. | A browser, over the public internet, designed for a phone first. |
| Asset structure | A tag database, organised the way the host organises tags. | Your own hierarchy, read by every module, with permissions granted on a branch of it. |
| Who it suits | A producer with facilities that need control, an automation group, and the scale to justify both. | A junior or mid-size producer who needs to know what is happening and be called when it changes. |
The honest summary
If you need control, you need a control system. If you need to know, and to be called, and to be able to answer what a value was doing last Tuesday, that is monitoring, and it is a smaller purchase than you have probably been quoted.
Most producers we talk to need both, at different sites, and the useful question is not which product wins. It is which sites justify a full deployment and which ones have been going unmonitored because they never will.