How Does SCADA Work?
Plain English
Explanation (2026)
An oil well in West Texas just triggered a high-pressure alarm. Within two seconds, an operations manager in Midland gets a text message, sees the exact sensor reading on a dashboard, and confirms the nearest field hand is already en route. That is SCADA at work. Here is exactly how it happens - no jargon, no acronym overload.
SCADA - Supervisory Control and Data Acquisition - is the technology that lets one person oversee hundreds of sensors, pumps, valves, and machines scattered across miles of pipeline, dozens of well pads, or an entire factory floor. Understanding how it works does not require an engineering degree. It requires understanding one simple concept: data has to travel from the physical world into a screen you can act on.
This article walks through that journey step by step, with real oil and gas examples, and explains why modern cloud SCADA has made the whole system dramatically simpler than the legacy systems that came before it.
The Big Picture: Five Layers of a SCADA System
Every SCADA system - regardless of vendor, industry, or vintage - is built around five layers. Data flows upward through each one, from the physical world to the operator's screen.
- Sensors and field devices - measure the physical process
- PLCs and RTUs - read sensors, execute local logic, package data
- Communication network - carry data from the field to the software
- SCADA software and historian - receive, store, and display data
- Operators and engineers - monitor dashboards, respond to alarms, issue commands
In a cloud SCADA system, layers 1 through 3 are the same as any traditional system. What changes is where layers 4 and 5 live - instead of on-site servers in a control room, the software runs in the cloud and operators access it through any web browser, on any device, from anywhere.
Layer 1: Sensors and Field Devices
Everything starts with measurement. Sensors convert physical conditions into electrical signals the rest of the system can read:
- Pressure transmitters - on wellheads, pipelines, vessels
- Flow meters - measuring liquid or gas volume through a pipe
- Temperature probes - inside furnaces, heat exchangers, tanks
- Level sensors - measuring fluid level in storage tanks or separators
- Motor status contacts - confirming whether a pump or compressor is running
- Valve position sensors - confirming whether a valve is open, closed, or partially open
Most sensors output one of two signal types: a 4–20 mA analog signal (where 4 mA = minimum measurement and 20 mA = maximum measurement) or a discrete digital signal (on or off, open or closed). These signals travel via wire to the next layer of the system.
Oil and gas example: A wellhead pressure transmitter reads 847 PSI. It converts that reading to a 12.3 mA analog signal on a wire running to the nearest RTU in the equipment skid. That 12.3 mA maps back to 847 PSI when the RTU reads it - a process that happens dozens of times per second.
Layer 2: PLCs and RTUs
Sensors cannot talk to software. A PLC (Programmable Logic Controller) or RTU (Remote Terminal Unit) sits between the sensors and the network. It does three things:
- Reads sensor signals - converts 4–20 mA analog signals into engineering units (PSI, degrees F, gallons per minute)
- Executes local control logic - if casing pressure exceeds 1,200 PSI, shut the surface safety valve immediately - without waiting for network communication
- Packages data for transmission - formats the readings into a protocol like Modbus or OPC-UA so the SCADA software can understand them
The distinction between PLCs and RTUs comes down to environment. PLCs are designed for manufacturing settings with reliable power and fast control loops - they might execute logic hundreds of times per second. RTUs are hardened for remote field environments: they run on solar power, handle cellular or radio communication, and are built to survive extreme temperatures. In the Permian Basin, most well pads run on RTUs.
For a deeper look at PLC programming, see our guide on Allen-Bradley and Siemens PLC programming in Texas.
Layer 3: The Communication Network
Once the RTU has packaged the data, it needs to send it somewhere. The communication network is the path that data travels from the field to the SCADA software. Options include:
- Cellular (4G LTE / 5G) - the most common choice for remote oil and gas sites today; low infrastructure cost, broad coverage in most of the Permian Basin
- Ethernet / fiber - used in facilities or plants where wired infrastructure already exists
- Licensed radio (900 MHz, 450 MHz) - used in areas with poor cellular coverage; requires licensed spectrum
- Satellite - last resort for extremely remote sites; higher latency and cost
In a traditional on-premise SCADA system, data travels over this network to a server sitting in a local control room or data center. In a cloud SCADA system, data travels over the same network - but instead of stopping at a local server, it flows directly to a cloud-hosted platform over a secure encrypted connection.
Layer 4: SCADA Software and the Historian
This is where raw data becomes actionable information. The SCADA software receives the data stream from field devices and does several things simultaneously:
Real-Time Display (HMI)
The HMI - Human Machine Interface - is the visual layer: dashboards, process mimic diagrams, live sensor values, and trend charts updating in real time. When an operations manager opens the Merobix dashboard and sees a map of 40 well pads with live pressures, temperatures, and production rates - that is the HMI.
Alarm Management
Every tag in the system can have high and low alarm limits configured. When a value breaches a limit, the SCADA software fires an alarm: it logs the event, highlights the affected asset on the display, and - in modern systems - sends a text or push notification to the on-call operator within seconds.
The Historian
Every reading from every sensor is time-stamped and stored in a historian database. This creates a continuous record of your entire operation. Need to know what the tubing pressure was on Well #14 at 3:47 AM on any given date? The historian has it. This data is invaluable for production optimization, regulatory reporting, and troubleshooting recurring failures.
Control Commands
SCADA is not just read-only. Authorized operators can issue commands from the dashboard - open a valve, start a pump, change a setpoint - and those commands travel back down the communication network to the PLC or RTU for execution. The round-trip from clicking a button to the field device responding typically takes under a second.
Layer 5: Operators and Engineers
Technology does not run an operation. People do. The SCADA system gives operations teams the visibility they need to make fast, confident decisions:
- Field operators use the HMI to monitor normal conditions, respond to alarms, and verify that recent work (valve changes, pump starts) had the expected effect
- Operations managers use dashboards to track production trends, compare asset performance, and identify which sites are underperforming
- Engineers use historical data to analyze trends, calculate run times and efficiency, and build predictive maintenance schedules
Traditional SCADA vs Cloud SCADA: What Actually Changed
The five-layer architecture described above has not changed. What has changed is where layers 4 and 5 live - and that shift has major practical consequences for operators.
Traditional On-Premise SCADA
In a traditional system, the SCADA software runs on servers located in a control room or data center at the site. This means buying and maintaining those servers, installing and licensing expensive SCADA software (often $20,000–$100,000+ for a full system), hiring IT staff or integrators to manage it, and building a network that connects every field site back to that central server room.
Cloud SCADA
In a cloud SCADA system, the software runs in the cloud - meaning the vendor's infrastructure. A small hardware gateway at each field site collects data from local RTUs and PLCs and sends it to the cloud over cellular or broadband. Operators access the software through a standard web browser on any device. There are no on-site servers, no software installations, and no IT infrastructure to maintain.
What this means for a small operator: A five-well pad that would have required a $40,000 SCADA server installation and six weeks of configuration can now deploy a cloud SCADA gateway in an afternoon and have live dashboards the same day. The monthly cost is a fraction of what a single IT support call used to cost.
For a full cost comparison, see our article on cloud vs on-premise SCADA total cost of ownership.
A Real-World Walk-Through: Oil Well Pressure Alarm
Let us trace a single alarm event through all five layers to make this concrete:
- Sensor (Layer 1): The casing pressure transmitter on Well #7 reads 1,340 PSI - above the configured high alarm limit of 1,200 PSI. It outputs a proportional analog signal to the RTU.
- RTU (Layer 2): The RTU reads the signal, converts it to 1,340 PSI, compares it against the alarm setpoint configured in its memory, and fires the local high-pressure alarm logic. It packages the reading with a timestamp and sends it over cellular to the cloud.
- Network (Layer 3): The RTU's cellular modem transmits the data packet to the Merobix cloud platform over an encrypted TLS connection. The round-trip takes under 200 milliseconds.
- SCADA Software (Layer 4): The platform receives the data, logs it to the historian, marks Well #7 as alarmed in the real-time display, and fires an SMS and push notification to the on-call operator. Elapsed time from physical event to notification: under 5 seconds.
- Operator (Layer 5): The on-call operator opens the Merobix mobile app, sees the current and trending pressure for Well #7, reviews the last 24 hours of data, and dispatches a field hand to investigate - all before physically leaving the truck.
Frequently Asked Questions
How does SCADA work in simple terms?
SCADA works by collecting data from sensors and field devices, sending it over a communication network to a central software system, and displaying it on dashboards operators can monitor and control in real time. Think of it as a nervous system: sensors are the nerve endings, the network is the spinal cord, and the SCADA software is the brain.
What is the difference between SCADA and a PLC?
A PLC controls a specific piece of equipment - a pump, a valve, a motor - by running local logic at the machine level. SCADA is the layer above: it connects to multiple PLCs and RTUs across an entire operation, collects their data, and gives operators a unified view of everything at once. PLCs execute control; SCADA provides visibility.
Does SCADA require on-site servers?
Traditional on-premise SCADA systems required dedicated servers, which added cost and IT maintenance. Modern cloud SCADA platforms like Merobix eliminate on-site servers entirely - a small data gateway sends data to the cloud over cellular or broadband, and operators access dashboards through any web browser.
How long does it take to set up a SCADA system?
Traditional SCADA deployments can take weeks or months due to server installation, software configuration, and custom programming. Cloud SCADA platforms like Merobix are designed for fast deployment - a pre-configured data gateway can be installed by a technician and have live data flowing to the dashboard within four hours.
Can SCADA work with existing field equipment?
Yes. SCADA systems are designed to read data from existing PLCs and RTUs using standard industrial protocols like Modbus, OPC-UA, and DNP3. You typically do not need to replace existing field hardware - the SCADA system connects to what you already have installed.
What industries use SCADA?
SCADA is used across oil and gas, water and wastewater, electric utilities, manufacturing, food and beverage, HVAC, mining, and agriculture. Any operation with distributed assets that need to be monitored and controlled remotely is a candidate for SCADA.
What does SCADA stand for in engineering?
SCADA stands for Supervisory Control and Data Acquisition. In engineering, it describes the technology that lets one person oversee hundreds of sensors, pumps, valves, and machines scattered across miles of pipeline, dozens of well pads, or an entire factory floor. Every SCADA system is built on the same five layers: sensors, PLCs and RTUs, a communication network, SCADA software with a historian, and the operators who monitor and act on the data.
Can SCADA work without the internet?
Yes - the field layers of a SCADA system do not depend on the internet. PLCs and RTUs execute local control logic on their own, so a high-pressure shutdown fires even if communication is down, and edge gateways can buffer data for up to 72 hours until the connection returns. Traditional on-premise SCADA runs entirely on a local network. Cloud SCADA does require a cellular, broadband, radio, or satellite link to deliver data to remote dashboards.
More in the Merobix Automation Fundamentals.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Modbus Application Protocol Specification - Modbus Organization
- Overview of DNP3 (IEEE Std 1815) - DNP Users Group
- OPC Unified Architecture Specification (IEC 62541) - OPC Foundation
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.