Picture the operator who bought the enterprise SCADA license three years ago. The server is humming. Half the tags are stale because the integrator left and the automation engineer never replaced him. The pumper is still texting tank levels to the back office because the dashboard nobody can trust doesn’t count as a source of truth. That is where a lot of SCADA software deployments end up on conventional wells. It is also preventable.
TL;DR: SCADA platforms for oil and gas (Ignition, VTScada, AVEVA, Rockwell, Siemens, AutoSol, zdSCADA, SCADAfarm, Kimray) are the right tool for instrumented facilities, high-per-site-value pads, and any operation that needs continuous supervisory control. It is the wrong tool for conventional wells where the per-site math never penciled or aging SCADA that is breaking down. In those cases, drop-in remote monitoring plus a pumper-first app delivers roughly 99% of the SCADA upside without the capex or maintenance drag. Works at 50 wells or 5,000.
Oil and gas SCADA software is the backbone of field operations for producers running instrumented facilities and high-per-site-value pads. It pulls readings from PLCs and RTUs at the wellhead, moves the data back to a server, displays it on a dashboard, alerts somebody when a variable goes out of range, and stores the history for analysis. It is a well-understood product category with a handful of dominant platforms, a long tail of regional integrators, and a pricing model that keeps conventional-well economics on the outside.
SCADA software for oil and gas falls into two broad groups: the platform vendors (Ignition, VTScada, AVEVA, Rockwell FactoryTalk View, Siemens WinCC) and oil-and-gas-specific platforms (AutoSol, zdSCADA, SCADAfarm, Kimray). Below them sits a layer of integrator firms who build the actual system an operator uses, and below that is the question of whether the operator needed SCADA in the first place.
This guide covers what the software actually does, how it is priced, and where simpler tools make more sense.
What SCADA Software Actually Does
A SCADA (Supervisory Control and Data Acquisition) platform in oil and gas does five things, in order:
- Polls field devices: RTUs and PLCs at the wellhead, at tank batteries, at compressor stations, at meters. The polling happens over radio, cellular, satellite, or fiber depending on the field.
- Normalizes the data: converting raw register values into engineering units (psi, degF, bpd, MCF).
- Displays it: typically in a control room, with screens showing well status, tank levels, pressures, flow rates.
- Alarms on exceptions: a tank level drops below setpoint, a pressure spikes, a pump shuts down. The alarm reaches the right person through voice, SMS, or email.
- Stores the history: so the engineer can pull a week of data on a well that acted up and see what changed.
The fancier features: setpoint changes pushed from the control room, automated shutdown logic, production reporting dashboards: layer on top of those five basics.
How SCADA Software Is Priced
Pricing models vary sharply across the platform vendors:
- Ignition (Inductive Automation): licensed per server with unlimited clients and tags. Considered operator-friendly because there is no per-tag licensing creep.
- VTScada (Trihedral): licensed per tag or per I/O point, with tiers for operator size.
- AVEVA (Wonderware / ClearSCADA lineage): licensed per tag and per named user, with enterprise pricing for larger deployments.
- Rockwell FactoryTalk View: licensed per client workstation, with SE and ME tiers.
- Hosted platforms (zdSCADA, SCADAfarm, Zedi): monthly SaaS pricing per well, with the host running the servers.
For a producer, the software license is often the cheapest line item. The real spend is instruments, RTUs, telemetry infrastructure, and integrator services. A full SCADA build-out for a greenfield pad can run six figures, and retrofit projects on legacy operations can run higher.
What SCADA Software Is Good At
Zooming out to the oil and gas SCADA pillar for a minute, SCADA is the right tool when:
- You have continuous, measured production that can’t be monitored by a human on a daily schedule.
- You have compression, water injection, saltwater disposal, or pipeline operations with dynamic states that change faster than a pumper can track.
- You have regulatory requirements for continuous measurement.
- Your per-site economics justify the infrastructure spend (capex, telemetry, integrator, ongoing controls support).
- You need exception-based management across dozens or hundreds of tags.
For high-rate horizontal programs, midstream operations, and central facilities with continuous flow, SCADA is the correct answer. That is true at 50 pads and 500.
What SCADA Software Is Bad At
SCADA becomes the wrong tool when:
- Your wells are conventional and the per-site cost of a full SCADA build never penciled against the per-site revenue.
- Your pumper already visits every well every day and can see everything SCADA would see.
- Your field has poor connectivity and the traditional telemetry install alone exceeds the visibility benefit.
- Legacy SCADA is breaking down, and the cost to keep it alive no longer justifies the upside.
- The 6-month install and the ongoing maintenance swamp the benefit at this specific site (independent of how many wells are in the portfolio).
In those cases, full SCADA is the wrong tool. The right answer is drop-in remote monitoring plus a pumper-first app.
On conventional wells where SCADA never penciled, drop-in remote monitoring plus pumper-captured data gives you visibility without the platform cost. Works at 50 wells or 5,000.
See how TinyPumper fills the gap →The Lightweight Alternative
TinyPumper is not SCADA and does not pretend to be. What it offers is the one thing SCADA exists to deliver: visibility into the well and the tank without the producer being there in person.
The trade is continuous versus close enough. Full SCADA gives you continuous data and real-time control. TinyPumper gives you hourly sensor reads on tank levels, pressures, and runtime (with threshold checks every 5 minutes and push alerts if something crosses the line), plus a pumper-first app for the tank gauge, run ticket, downtime, and comments. For a conventional well where SCADA never penciled, that is plenty. For an aging SCADA install that has turned into a maintenance drag, it is the drop-in.
TinyPumper was built for exactly this model. Solar-powered gateway. Radar on top of the tank. Pressure sensor at the wellhead. Installs in 10 minutes. No trenching, no integrator. Flat rate per site, unlimited sensors at that location. Paired with GreaseBook, the pumper-entered data and sensor-automated data live in one screen. This works at 50 wells and at 5,000 (a meaningful share of our book runs well above 1,000 wells, and the value prop holds).
For producers running a mix of instrumented facilities and conventional wells, the pragmatic answer is usually both: SCADA on the facilities and pads that need it, TinyPumper on the sites where SCADA doesn’t pencil.
The pro producer does not confuse software category with problem category. The pro producer asks what the site needs to see, what the downside of a missed day costs, and what staff the operation has to maintain anything fancy. Then they pick software that fits that answer. This is who we are in the oil patch. We don’t buy feature lists. We buy outcomes on the lease.
Amateur vs Pro: How Producers Shop SCADA Software
| The amateur… | The pro… |
|---|---|
| Compares platforms on feature-count tables | Compares platforms on total deployed cost at their actual site |
| Asks the vendor how much the license is | Asks the integrator how much the build-out plus three years of support is |
| Treats “we have SCADA” as a status signal | Treats “we have the right tool per site” as the outcome |
| Assumes one platform fits conventional wells and instrumented pads equally | Runs SCADA where it pays back and drop-in monitoring where it doesn’t |
| Hopes the pumper will use the SCADA dashboard too | Keeps the pumper on a mobile-first app that syncs offline |
How to Decide
Four questions cut through the marketing:
- What does 24 hours of undetected downtime cost on a typical site? This is the real SCADA ROI number.
- Does the pumper already go to the site every day? If yes, the pumper is cheaper and more complete than any telemetry.
- Is the connectivity already there? In remote fields, the telemetry install is often the bigger cost than the software.
- How tight is your operational staff? SCADA without an automation engineer to maintain it degrades fast. If you don’t have the staff, hosted SCADA or drop-in remote monitoring is safer than a neglected SCADA stack.
What To Avoid When Shopping SCADA Software
- Don’t fall for The SCADA Silo. A platform that only talks to its own historian, its own HMI, and its own vendor’s cloud keeps data locked where nobody outside the control room can use it. Pick tools that export cleanly.
- Don’t beat The Paper Lag with a six-month install. If the core problem is that pumper data arrives three weeks late, the fix is a mobile-first capture app, not an enterprise SCADA platform. Solve the capture problem first.
- Don’t buy software without a maintenance plan. Any serious SCADA stack needs an automation engineer or a live integrator partnership. Licensing a platform and then abandoning the support contract is how six-figure investments rot.
- Don’t assume hosted SCADA is always cheaper. The monthly SaaS number looks friendly. The integrator build-out to get your instruments talking to it is still there. Get the full quote.
- Don’t ignore the connectivity bill. In rural basins, telemetry often costs more per year than the software license. Price it end to end before you sign.
Wrong Fit for This Page
If you are already running a large horizontal program with hundreds of continuous-measurement wells, full telemetry, and a centralized operations center, you have already made the SCADA call. Your question is which platform and which integrator, not whether to buy. This page is for the producer trying to decide whether full SCADA is worth the money at a specific site or a specific conventional-well program, and whether something simpler does the job.
FAQ
Can TinyPumper replace SCADA software completely?
For instrumented facilities and high-per-site-value pads where full SCADA already pays back, no. For conventional wells where the per-site SCADA math never penciled (or legacy SCADA that is breaking down), yes. TinyPumper delivers roughly 99% of the upside of SCADA without the cost or complexity, and that holds at 50 wells or 5,000.
What is oil and gas SCADA software?
SCADA software polls field instruments at wells, tanks, and facilities; normalizes the data; displays it on dashboards; alarms on exceptions; and stores the history. It is the standard tool for continuous remote monitoring in oil and gas.
Is there free oil and gas SCADA software?
There are free open-source SCADA options (Rapid SCADA, some lightweight platforms), and Ignition offers a free Maker Edition for personal use. Commercial oil and gas operations typically license paid platforms because of support, security, and oilfield-specific features.
How much does oil and gas SCADA software cost?
The software license varies from a few thousand dollars per server (Ignition) to tens of thousands for enterprise deployments (AVEVA, Rockwell). Total SCADA project cost including instruments, telemetry, and integration usually runs much higher: six figures for a full pad build-out is common.
Do producers running conventional wells need SCADA software?
Not automatically. Producers running conventional wells where the per-site SCADA math never penciled (or legacy SCADA that is breaking down) often get better ROI from drop-in remote monitoring plus a pumper-captured data app than from a full SCADA platform. The value prop holds at 50 wells or 5,000.
Related Pages
- Oil and gas SCADA: the pillar guide to SCADA in oil and gas.
- Oil and gas SCADA companies: which vendors sell what and where each one fits.
- Ignition SCADA alternative: when Ignition is overkill for a smaller operation.
- What is SCADA: the definition and how SCADA compares to HMI and DCS.
TinyPumper is built for the sites where that math never worked (or no longer works). Same question: "what's happening at my wells today." Different economics. Install cost of one RTU can pay for years of TinyPumper.
See how TinyPumper works →