Written for the producer about to sign a SCADA purchase order, not for the sales engineer writing the quote. If you’re the one who has to defend the capex, keep the integrator honest, and explain to the CFO why the per-site math works, keep reading.

Picture the SCADA integrator call. Two hours on a Tuesday. The deck has 47 slides. By the end, the scope has grown from tank levels at 20 sites to a full host system, a historian, an HMI operator station, and an 18-month rollout plan. Eighteen months later the hardware is installed and the alarm console is muted because nobody has time to tune it. The HMI in the office is still bookmarked by the controls engineer who left last spring. Nobody watches the screen. That is the failure mode this guide is built to prevent.

SCADA stands for Supervisory Control and Data Acquisition. In oil and gas, it is the stack that pulls data from sensors at the wellhead, tank battery, compressor station, or disposal well, sends it over cell, radio, or satellite to a server, and gives the office a live view of what is happening. The same stack can send commands back to start a pump, close a valve, or shut in a well. This guide walks through how the layers fit together, what the real costs look like, which vendors show up most often, and the honest call on when SCADA earns its keep versus when a simpler monitoring approach is the better fit.

The short version: SCADA is powerful and expensive. For unconventional pads, central compression, gas plants, and large facilities where downtime is measured in dollars per hour, it is table stakes. For conventional wells where the per-site math never penciled, or legacy SCADA that is breaking down and not worth the cost to babysit, it is almost always overkill. Well count is not the right axis here (a 50-well operator and a 5,000-well operator can both run conventional wells where SCADA does not pay back). Facility complexity and per-site economics are. Nobody else in this space will tell you the second half of that sentence, which is exactly why we’re starting there.

This post is for you if:

  • You’re scoping a SCADA rollout and want the honest read on where it pays back versus where a lighter monitoring stack wins.
  • You have legacy SCADA on conventional sites and the maintenance load is eating the return.
  • You run anywhere from 50 to 5,000 wells and the per-site economics question is already on your desk.
  • You want to know what real rollouts cost, which vendors matter, and which mistakes kill SCADA programs inside year one.

If none of that fits, the oilfield monitoring pillar covers the broader monitoring category and oilfield IoT covers the cloud-first sensor-first side.

What SCADA Actually Is

The term gets thrown around loosely. In practice, SCADA has four distinct layers.

1. Field devices. Sensors, transmitters, and final control elements at the site. A radar tank level sensor, a pressure transmitter on a flowline, a motor valve on a dump line, a flow meter on a separator. These are the things doing the physical measurement or control.

2. PLCs and RTUs. Programmable logic controllers and remote terminal units sit in a cabinet at the site, take the signals from the sensors, run basic logic (close this valve when that pressure hits a threshold), and hand the data off to the communication layer. RTUs are more common at remote wellheads; PLCs are more common at facilities with more instrumentation.

3. Communications. Cellular (AT&T, Verizon, FirstNet), licensed radio, unlicensed radio, satellite (Iridium, Starlink), or wired. This layer is the thing that most often fails and most often drives monthly cost. The pumper does not care whether it is polled or report-by-exception; they care whether the data shows up.

4. The host system. Software on a server (on-prem or cloud) that receives the data, stores it in a historian, displays it on screens (HMIs), triggers alarms, and lets operators issue commands back to the field. Ignition, Cygnet, eLynx, and Canary are common names here.

All four have to work for SCADA to work. A gap in any one layer (a failed sensor, a broken comms radio, a host system that crashed overnight) takes the whole thing down.

What SCADA Does in an Oil and Gas Operation

Strip the marketing away and SCADA does four jobs.

Continuous data collection. Unlike a pumper doing a daily round, SCADA is polling every few seconds to every few minutes. For production volumes that matters less. For pressures, runtime, and trip events it matters a lot.

Alarming. High tank, low suction, ESD, gas detection, compressor trip. The alarms fire to a console, to a phone, or to a pumper on call. Good SCADA alarm philosophy is harder than it sounds; most systems over-alarm out of the gate.

Remote control. Starting and stopping pumps. Opening and closing valves. Adjusting setpoints. Resetting compressors. All of it has safety constraints, role-based permissions, and an audit trail.

Historical trending. A year of tubing pressure history at one-minute resolution is a different conversation than spot readings from the pumper. Engineers rely on this for optimization, failure diagnosis, and type curve work.

Which One Do You Actually Need?

Forget the vendor deck. Here is the honest read on SCADA versus the alternatives, by situation.

If you… Then… Because
Run a compressor station, gas plant, or disposal well where downtime is dollars per hour Full SCADA is table stakes Supervisory control and alarm logic is the job SCADA was built for
Have high-rate horizontal pads where per-site revenue dwarfs per-site capex Full SCADA pencils easily The ROI math works at any scale (50 horizontal pads or 500)
Run legacy SCADA that is breaking down on conventional wells A drop-in monitoring alternative like TinyPumper is the honest fix The maintenance drag eats the return; replacement is cheaper than babysitting
Have conventional wells and tank batteries where SCADA never penciled Phone-first field app plus flat-rate per-site monitoring Roughly 99% of the upside without the wiring, the electrician, or the IT burden
Have a mix of unconventional facilities and conventional long-tail wells Run both stacks SCADA where the economics earn it, TinyPumper on the rest

Not sure if SCADA is the right lift for your operation?

The 2-minute fit quiz takes well count, facilities, and team into account. We'll tell you where the honest threshold is.

Take the quiz

The Real Categories of SCADA in Oil and Gas

There are a few distinct flavors in the market, and the vendor conversations go sideways when the categories get mixed up.

1. Full-stack enterprise SCADA

Systems like Ignition, Canary, and OsiSoft PI do the host, historian, HMI, and reporting all together. Built for operators running hundreds to thousands of sites, with a dedicated controls team. Licensing is significant, install takes months, and the result is a deep, flexible platform. See Ignition SCADA alternatives for context on the smaller-operator lift.

2. Hosted oil and gas SCADA

Vendors like Cygnet (Weatherford), eLynx, Zedi (Emerson), and TelVent (Schneider) host the SCADA stack in their cloud and sell it as a service. The operator rents the host, the historian, and the HMI on a per-site monthly basis. Lower capex, higher opex, faster rollout. Common for unconventional operators who don’t want to run their own controls team. See oil and gas SCADA companies for the landscape.

3. Purpose-built upstream SCADA software

Narrower systems designed specifically for upstream production. Oil and gas SCADA software tends to be simpler than the enterprise platforms but more opinionated for oilfield use cases. Good middle ground for mid-sized operators.

4. Open-source or hobbyist stacks

Ignition (actually commercial but flexible), Node-RED, OpenHAB-adjacent setups. Useful for producers with strong in-house automation expertise. Not common in production oilfield environments but worth mentioning because engineers sometimes ask.

What SCADA Costs in Oil and Gas

Real numbers. Ranges are wide because every project has a different starting point.

Item Low end High end Notes
Per-site hardware (RTU, sensors, cabinet, install) $3,000 $25,000 Depends on how much is already there and what’s being metered
Per-site monthly comms + hosting $50 $250 Cellular plans, hosted SCADA fees, alarm services
Host platform software (enterprise) $50,000 $500,000+ One-time license; annual support is 20 percent of that
Host platform software (hosted SaaS) $0 up front Rolled into per-site fee Opex play
Integrator labor (initial rollout) $500 / site $5,000 / site Wild variance by region, scope, and whether the operator’s team does any of the work
Ongoing controls support $80K / year for a tech $250K / year for an engineer Someone has to keep the system alive

A 100-site SCADA rollout with hosted software, moderate instrumentation, and a good integrator tends to land somewhere between $500K and $1.5M up front plus $100K to $300K per year operating. That is a real number, not a vendor’s happy-path estimate.

When SCADA Earns Its Keep

Forget well count. The axes that actually matter are facility complexity and per-site economics.

Central facilities that have to stay up. Compressor stations, saltwater disposal, gas plants, inlet separation. Unplanned downtime at a facility costs real money per hour. That is where SCADA pays back fastest.

Safety-critical operations. H2S gas detection, fire and gas, ESD systems. The alarm and shutdown logic has to be instrumented. Paper won’t do it.

Optimization-driven operations. Plunger lift, gas lift, ESPs, rod pump optimization. The control loop runs on SCADA data. Without it, the optimization is guesswork.

Regulatory or midstream interface requirements. Custody transfer, air permit continuous monitoring, midstream allocation that needs flow data every hour. Some contracts and permits require the instrumentation.

Unconventional pads with enough per-site value. High-rate horizontals, enhanced recovery, and mixed production/injection pads where the per-site spend is a small fraction of the per-site revenue. SCADA earns its keep here at any scale (a producer running 50 horizontal pads and a producer running 500 both sign off on the same ROI math).

If none of those apply (meaning this is a conventional well where SCADA never penciled, or legacy SCADA that has turned into a maintenance drag), a phone-based field data capture tool plus remote monitoring that drops in without a trench or an integrator is probably the honest answer. See oilfield monitoring for the stack options.

Where SCADA Breaks Down

Three recurring failure modes.

Over-alarming. The system goes live, every deadband is wrong, and within a week the pumpers and engineers have muted the alarm channel. Rebuilding trust in the alarm list is harder than the original setup. Good SCADA programs spend time on alarm philosophy up front, even though it is unglamorous work.

The SCADA Silo. The host system is beautiful on the office wall. The pumper has no idea what it says, gets no alarms, and still runs the same paper route. SCADA without a mobile layer for the field team is half a system. The pairing pattern here is SCADA at facilities plus a phone tool like Greasebook or TinyPumper for the wellheads and the route.

No budget for ongoing support. The initial rollout gets funded. The full-time tech or engineer to keep the system alive does not. Within 18 months the historian is full, the alarms haven’t been tuned since go-live, and half the RTUs are offline.

Amateur vs Pro: How Operators Spec a SCADA Rollout

The amateur… The pro…
Lets the integrator scope from the host platform down to the sensors Scopes from the site economics up; only buys the layers that earn their keep
Signs a fixed-facility rollout and hopes the alarms tune themselves Budgets for alarm philosophy work before go-live and a tech to keep it tuned after
Treats SCADA as the monitoring answer for every well in the portfolio Runs SCADA where the per-site math pencils and a lighter stack on the conventional long tail
Lets each vendor ship its own dashboard until five logins later nobody opens any of them Picks the consolidation layer (historian + field app) before vendor number two is added
Leaves the pumper out of the rollout plan Designs the alert path backward from the pumper’s phone

The best operators we see do not get fancier SCADA. They get disciplined SCADA. Alarm philosophy funded up front. Ongoing controls support budgeted alongside the hardware. Facility SCADA paired with a phone-first tool for the field team. The SCADA Silo closed before it has a chance to open.

SCADA at the facility, phone app in the field

Most operators end up here. TinyPumper is the phone-first layer for the route. See how it fits with your SCADA stack.

See TinyPumper

The Main SCADA Vendors Operators Encounter

Not a ranking. Just the names that show up most often in operator conversations and a one-line honest read on each.

  • Ignition (Inductive Automation). Flexible, scriptable, unlimited tags. Requires real in-house expertise. Popular with operators running their own controls teams.
  • Cygnet (Weatherford). Upstream-specialized, hosted or on-prem. Common in unconventional. Honest workhorse.
  • eLynx. Hosted SCADA, oilfield-focused, strong alarm and integration tooling. Mid-sized operators.
  • Zedi (Emerson). Hosted SCADA with strong well-test and gas flow measurement. Canadian operators and well measurement use cases.
  • Canary Labs. Historian-first, often paired with Ignition or other HMIs.
  • OsiSoft PI. Enterprise historian, common in large operators and midstream. Heavy.
  • Wellaware, Novatel, Freewave, SignalFire, FreeWave. Telemetry hardware vendors, often selling alongside a host SCADA.

See oil and gas SCADA companies and oil and gas SCADA software for a deeper read on the landscape.

What Is SCADA Actually? The Plain-English Version

If an operator is still wrapping their head around the concept, what is SCADA walks through the fundamentals without vendor framing. Useful for a new engineer, a new controller, or an operator evaluating whether to bring SCADA in for the first time.

SCADA vs. Automation vs. IoT

These terms get used interchangeably. They are not the same.

  • SCADA is the historical term for the stack that monitors and supervises distributed field equipment. It implies PLCs/RTUs, a host system, and an HMI.
  • Oil and gas automation is the broader idea of using logic and controls to make the field run without constant human intervention. SCADA is one tool inside automation. See oil and gas automation for the TP-3 pillar.
  • IoT (Internet of Things) is a newer framing where sensors connect directly to the cloud, often over cellular or LPWAN, often without a traditional PLC layer. See oilfield IoT for the TP-4 pillar.

In practice, modern oilfield monitoring stacks mix all three. A SCADA host pulls data from traditional RTUs and from cellular IoT sensors and from cloud-connected flow meters, and the distinction between automation and SCADA blurs.

What To Avoid Before You Sign the PO

  • Don’t let the integrator scope down from the host platform. The SCADA Silo starts with the deck that begins at the historian. Scope from the site economics up. Buy only the layers that earn their keep.
  • Don’t skip the alarm philosophy work. An untuned alarm list is a muted alarm list inside a week. If alarm philosophy is not on the scope of work, the rollout is going to look live and be deaf.
  • Don’t deploy SCADA without a field layer. The office HMI is half a system. The pumper needs alerts on a phone. Pair SCADA with a phone-first tool for the route before day one, not after the silo has formed.
  • Don’t buy SCADA to avoid a monitoring decision. For conventional wells where the math never penciled, SCADA is the wrong answer no matter how good the demo looks. A flat-rate per-site monitoring layer like TinyPumper is the honest fit on those sites at any scale (50 wells or 5,000).
  • Don’t fund the rollout without funding the support. A SCADA program without an ongoing controls tech or engineer budget is a program that will be dead in two years. If the ongoing cost can’t be funded, the initial cost shouldn’t be either.

Who SCADA Is Not For

Producers running conventional wells where SCADA never penciled. The per-site capex, wiring, IT load, and ongoing maintenance never hit an ROI the operator could defend. A phone app for the pumper plus drop-in remote monitoring (TinyPumper) is the honest answer at any well count (50 wells or 5,000).

Producers with aging SCADA that is breaking down. The cost to maintain (sensor replacements, servicing, paying someone to babysit the stack) is no longer justified by the upside. Swapping it out for a drop-in remote monitor costs a fraction and kills the maintenance drag.

Producers wanting one vendor for everything. SCADA vendors are good at SCADA. They are not typically good at paper replacement, production software, regulatory reporting, or full ERP. Trying to force one system to do all of that is how expensive rollouts fail.

Producers without ongoing controls support. A SCADA rollout without a budget line for the person maintaining it is a rollout that will be dead in two years. If the ongoing cost can’t be funded, the initial cost shouldn’t be either.

Need the phone-first layer that plays well with your SCADA?

TinyPumper handles the route, the manual gauge, and the stuff SCADA can't see. Pairs with any host system.

Start with TinyPumper Or take the fit quiz

About the author: Greg Archbald is the founder of GreaseBook and TinyPumper. He built both products from inside the oil patch and has spent 15+ years on the operator side of oil and gas technology.

Frequently Asked Questions

What does SCADA stand for in oil and gas? Supervisory Control and Data Acquisition. In oil and gas it refers to the combined hardware and software stack that monitors wells, tanks, and facilities, triggers alarms, and lets the office start, stop, or adjust equipment remotely.

Is SCADA the same thing as a DCS? No. A distributed control system (DCS) is a tighter, lower-latency control system typical of refineries and continuous-process plants. SCADA is built for geographically distributed, slower-update-cycle operations like upstream production. They overlap, but the use cases and the price tags are different.

How much does an oil and gas SCADA rollout cost? For a 100-site rollout with hosted software and moderate instrumentation, plan on $500K to $1.5M up front and $100K to $300K per year operating. Per-site costs range from $3K for a simple cellular telemetry install up to $25K+ for a fully instrumented facility.

Can I run SCADA and a phone-based field data app at the same time? Yes, and most operators do. SCADA handles the facilities and instrumented wellheads; the phone app handles the manual gauge, the daily pumper round, and the wellheads that don’t have RTUs. They cover different parts of the operation.

Do I need SCADA for state regulatory reporting? Not for most upstream production reporting. State regulators care about monthly or daily volumes, not second-by-second data. SCADA helps with the data capture and reduces pumper rounding errors, but the reporting happens at the production software layer. See oil and gas regulatory production reports for the reporting side.