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 contract pumpers and small operators skip SCADA 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.

SCADA fits some operations. Others it doesn't.

For contract pumpers and small operators, daily pumper-captured data is often the honest answer.

See how TinyPumper fits →

Where SCADA Is the Wrong Answer

SCADA becomes the wrong tool when:

  • The wells are stripper-rate and the economic downside of 24 hours of undetected downtime is small.
  • A pumper is already visiting each well every day and could see everything SCADA would show.
  • The field has poor connectivity and the telemetry install exceeds the visibility benefit.
  • The operator has no automation staff to maintain the system.
  • The operator is a contract pumper serving multiple clients who won’t share in the SCADA build cost.

In those cases, the honest answer is a pumper-captured data app, not SCADA. TinyPumper is a common alternative for contract pumpers and small operators. It replaces the “see what’s happening at every well” job of SCADA with a phone in the pumper’s pocket and a dashboard the operator can open from anywhere. No RTUs, no radios, no integrator.

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 operators and contract pumpers 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. SCADA is hardware at every well. TinyPumper is the pumper’s phone. If you need real-time control loops and alarm dispatch across a high-volume field, this isn’t that. If you need ‘what’s happening at my wells today,’ it is.

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 ten wells doing ten million dollars a year.

For the other 95% of American oil production: strippers, marginals, small independents: it's overkill. TinyPumper puts the pumper's eyes on every tank via a phone in the pocket. No RTU, no radio, no integrator. Because the math on SCADA for a 10-barrel-a-day well doesn't work.

See how TinyPumper works →
**P.S.** Most operators asking "what is SCADA" are actually asking "do I need it." The honest answer is: probably not, if you are under 100 wells with predictable artificial lift. A pumper-first mobile app covers the same ground for less money and less maintenance.