Picture the pumper’s truck rolling up to a tank battery at 6 a.m. He climbs the steps, pops the thief hatch, drops a gauge line, and writes a number on a clipboard. Six miles away, in a control room that doesn’t exist yet, a SCADA system would have read that same tank level four times overnight and emailed a haul alert. One costs a truck and a pair of boots. The other costs six figures and an automation engineer. Both answer the same question.

TL;DR: SCADA stands for Supervisory Control and Data Acquisition. In the context of SCADA in oil and gas, it is the combination of field sensors, telemetry, and server-side software that lets a producer see what is happening at every wellhead, tank, and facility from a central location. It is the right tool for instrumented facilities, high-per-site-value pads, and operations that need continuous supervisory control. On conventional wells where the per-site math never penciled (or legacy SCADA that is breaking down), drop-in remote monitoring plus a pumper-first app covers the same visibility job at a fraction of the cost. Works at 50 wells or 5,000.

SCADA stands for Supervisory Control and Data Acquisition. In oil and gas, SCADA is the software, hardware, and telemetry system that lets an operator see what is happening at every wellhead, tank, meter, and compressor from a central location. A pumper in a truck with a phone is one way to monitor wells. SCADA is the other way.

At its simplest, SCADA does four things: it reads data from sensors in the field, moves the data back to a server, displays it to a human operator, and stores it for later. Anything more than that: automated control, alarm dispatch, reporting: is built on top of those four basics.

This is a plain-language explanation of what SCADA is in oil and gas, how it differs from related systems, and when it is the right tool versus when something simpler does the job.

SCADA Isn’t the Only Way to See Your Wells.

See how producers skip SCADA on conventional wells and still keep tabs on every tank.

See TinyPumper →

The Four Things SCADA Actually Does

  1. Data acquisition. A SCADA system connects to PLCs (programmable logic controllers) or RTUs (remote terminal units) in the field. Those devices read sensors: pressure transmitters, flow meters, tank levels, temperature probes: and report the readings back.
  2. Communication. The data has to get from the field to the server. SCADA systems use radios, cellular modems, satellite modems, or fiber, depending on the field’s connectivity options.
  3. Supervision. Once the data arrives, the SCADA software displays it on screens in a control room (or on a laptop). Operators watch the displays, look for alarms, and make decisions.
  4. Control. In more mature deployments, operators can send setpoint changes back to the field: opening or closing valves, starting or stopping pumps, adjusting flow setpoints.

Every SCADA deployment does the first three. The fourth (active control) is the piece that separates basic monitoring SCADA from full supervisory control.

How SCADA Shows Up in Oil and Gas

A typical upstream SCADA deployment looks like this:

  • At the wellhead or tank battery, an RTU polls local sensors: tank level, pressure, flow, pump runtime.
  • A telemetry link (cellular, radio, satellite) carries the data back.
  • A SCADA server (often Ignition, VTScada, AVEVA, or AutoSol) receives the data and displays it on operator screens.
  • Alarms route to the right person when something goes out of range.
  • A historian stores the data for later analysis.

Midstream operations (compression, gathering, pipelines) use SCADA the same way, with much higher stakes for continuous control. Downstream refineries use distributed control systems (DCS), which is related but not the same thing.

SCADA vs HMI vs DCS vs MES

The terminology around industrial control gets mushy, so here is the clean version:

  • HMI (Human-Machine Interface) is the screen a local operator looks at to control one piece of equipment. An HMI at a compressor station is the touch screen on the compressor.
  • SCADA is the system that aggregates data from many HMIs, RTUs, and PLCs across a wide geographic area into a central supervisory view. A SCADA system watching 200 wells across a county is not an HMI.
  • DCS (Distributed Control System) is closer to SCADA in function but different in topology: DCS is typically used in one facility (a refinery, a gas plant, a chemical plant) with tightly-coupled process control and automation logic. Emerson DeltaV and Honeywell Experion are DCS products.
  • MES (Manufacturing Execution System) sits above SCADA and DCS, typically in manufacturing contexts, tracking production workflow and quality.

In most of oil and gas, you will encounter SCADA (upstream and midstream) and DCS (refineries and gas plants). HMI is a component inside both. MES is rare in upstream operations.

Where SCADA Is the Right Answer

SCADA is the correct tool when:

  • Continuous monitoring is required by regulation or by economics.
  • Downtime on a single well or facility costs enough to justify the telemetry infrastructure.
  • The operation is geographically dispersed and a pumper can’t cover it daily.
  • Compression, water injection, or gathering operations have dynamic states that change faster than human observation can track.
  • The operator has (or will hire) an automation team to maintain the system.

For high-rate horizontal programs, midstream, and large legacy fields, SCADA is the standard answer and the right one.

The pro producer does not ask “what is SCADA” as a shopping question. The pro producer asks what the site actually needs to see, what the cost of missing a day looks like, and what staff is around to keep any of it alive. Then they pick the tool that matches. This is how we do it in the oil patch. The tool serves the site, not the other way around.

Amateur vs Pro: How Producers Evaluate SCADA Fit

The amateur… The pro…
Asks “should I have SCADA” as a yes-or-no question Asks which sites need SCADA and which don’t
Assumes every producer at scale runs full SCADA Knows plenty of mixed-portfolio producers run full SCADA on facilities and drop-in monitoring on conventional sites
Treats SCADA as a modernization badge Treats SCADA as one tool among several, picked per-site
Lets a neglected SCADA server define “we have monitoring” Retires the dying install and replaces it with a stack somebody will actually maintain
Hopes the pumper will migrate to the SCADA dashboard Keeps the pumper on mobile capture because that is where field data really lives
SCADA fits some operations. Others it doesn't.

On conventional wells where the per-site SCADA math never penciled, daily pumper-captured data plus drop-in remote monitoring is often the honest answer.

See how TinyPumper fits →

Where SCADA Is the Wrong Answer

SCADA becomes the wrong tool when:

  • The wells are conventional and the per-site economic downside of 24 hours of undetected downtime doesn’t justify the capex, wiring, and ongoing controls support.
  • A pumper is already visiting each well every day and could see everything SCADA would show.
  • The field has poor connectivity and the traditional SCADA telemetry install exceeds the visibility benefit.
  • Legacy SCADA is breaking down, and the cost to keep it alive no longer justifies the upside.

In those cases, the honest answer is drop-in remote monitoring plus pumper-captured data, not a full SCADA stack. TinyPumper is a common answer here. Solar-powered gateway, radar on top of the tank, pressure sensor at the wellhead, plus a phone in the pumper’s pocket. It replaces the “see what’s happening at every well” job of SCADA. No RTUs, no radios, no integrator. That value prop holds at 50 wells or 5,000.

What To Avoid When Deciding on SCADA

  • Don’t fall for The SCADA Silo framing. Any monitoring stack (SCADA or lighter) that traps data where the pumper, the back office, and the engineer can’t all see it is a failure, regardless of vendor. Pick for data access, not just data capture.
  • Don’t confuse The Paper Lag with a SCADA problem. If production numbers arrive three weeks late, the root cause is paper capture, not missing telemetry. Fix the capture layer first.
  • Don’t buy SCADA to silence a sales deck. If an instrumented facility or high-rate pad justifies SCADA, buy it with confidence. If the pad is conventional and the math doesn’t carry it, don’t sign to look sophisticated.
  • Don’t run a SCADA system with no one to maintain it. A server sitting unpatched for three years after go-live is how producers end up paying for data they can’t trust. No automation engineer means hosted SCADA or drop-in monitoring, not a self-hosted install.
  • Don’t skip the pumper’s phone. Wherever the data lands (SCADA or otherwise), the pumper on the lease is the last mile. Design for his screen first.

Wrong Fit for This Page

If you are searching for “what is SCADA” from a water utility, power grid, or manufacturing context, this page is not for you: SCADA is a much broader category than oil and gas. This page is written specifically for producers in upstream or midstream oil and gas who are trying to understand what SCADA is, what it costs, and whether it fits their operation.

FAQ

Is TinyPumper a SCADA system?

No, and that’s the point. TinyPumper is drop-in remote monitoring plus a pumper-first app: solar-powered gateway, radar on top of the tank, pressure sensor at the wellhead, 10-minute install. If you need real-time control loops and alarm dispatch across instrumented facilities and high-per-site-value pads, this isn’t that. If you need “what’s happening at my wells today” on conventional wells where SCADA never penciled (or legacy SCADA is breaking down), it is. Works at 50 wells or 5,000.

Can AI replace SCADA?

Not directly. AI tools add analytics and anomaly detection on top of SCADA data, but they do not replace the data acquisition and telemetry layer. SCADA is the plumbing that brings the data in; AI is an optional analytical layer on top.

Can a PLC run without SCADA?

Yes. A PLC runs control logic locally on the equipment and does not require SCADA to function. SCADA simply gives the operator visibility and supervisory control across many PLCs at once.

What is the difference between SCADA and HMI?

An HMI is the local screen on one piece of equipment. SCADA is the aggregated supervisory system that pulls data from many HMIs, PLCs, and RTUs across a wide area. An HMI is a component; SCADA is a system.

Is SCADA only used in oil and gas?

No. SCADA is used across utilities (power, water, wastewater), manufacturing, transportation, and other industries. This page focuses on SCADA in oil and gas specifically, where the use cases and economics are distinct.

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

SCADA is the right answer for instrumented facilities and high-per-site-value pads.

For conventional wells where the per-site math never penciled (or legacy SCADA that's breaking down), it's overkill. TinyPumper puts tank levels, pressures, and runtime on one dashboard with a 10-minute install. No RTU, no radio, no integrator. Works at 50 wells or 5,000.

See how TinyPumper works →
**P.S.** Most producers asking "what is SCADA" are actually asking "do I need it." The honest answer depends on facility complexity and per-site economics, not well count. If your wells are conventional and SCADA never penciled (or the SCADA you have is breaking down), drop-in remote monitoring plus a pumper-first app covers the same ground for a fraction of the cost.