SCADA vs PLC: What Each Does, Where One Ends and the Other Begins
SCADA vs PLC: What Each Does, Where One Ends and the Other Begins
TL;DR: A PLC (Programmable Logic Controller) executes control logic in real time and drives physical outputs — motors, valves, actuators. SCADA (Supervisory Control and Data Acquisition) is a software layer that reads data from many PLCs across a site, displays it to operators, logs it historically, and manages alarms. The PLC controls the machine. SCADA watches the plant. A plant has one SCADA system and dozens or hundreds of PLCs.
These two terms are often thrown together as if they are the same thing. They are not. Every industrial site has PLCs. Most medium-to-large sites also have SCADA. But the jobs they do are completely different, and mixing them up leads to misunderstandings about how automation actually works.
What a PLC Does
A PLC executes a control program — typically ladder logic — on a continuous scan cycle of 5 to 50 milliseconds. Every scan it reads its physical inputs (sensors, pushbuttons, limit switches), runs the program logic, and updates its physical outputs (motor contactors, solenoid valves, indicator lamps). This loop runs autonomously. The PLC does not need a human watching, an HMI connected, or a SCADA server reachable. If the control logic says start the pump, the pump starts.
Key characteristics of a PLC:
- Deterministic: the same input conditions produce the same output in the same scan, every time.
- Safety-critical: the PLC enforces interlocks and e-stop logic. If the e-stop is pressed, the output goes off in the current scan because the logic says so — regardless of what SCADA thinks.
- Directly wired: sensors and actuators are hard-wired to I/O cards on the PLC chassis.
- Scope: one machine or process unit. A pump skid has one PLC. A conveyor section has one PLC.
What SCADA Does
SCADA is a software application running on a server (or set of servers) that collects data from many PLCs across a site, displays it on operator workstations, logs it to a historian database, and manages alarms. SCADA does not control anything directly — it reads PLC data, displays it, and allows supervisory operators to send setpoints and commands back to PLCs.
Key characteristics of SCADA:
- Supervisory: it watches and reports. It does not run real-time safety logic.
- Multi-node: it connects to dozens or hundreds of PLCs, RTUs, and field devices.
- Historical: SCADA historian databases store process values at configured intervals for trending, reporting, and compliance.
- Alarming: SCADA aggregates alarms from all connected PLCs into one operator view with acknowledgement tracking.
- If the SCADA server goes offline, every PLC it was watching keeps running. The machines do not stop.
Common SCADA platforms: Ignition (Inductive Automation), WinCC SCADA (Siemens), iFIX (GE), FactoryTalk View Site Edition (Rockwell).
Side-by-Side Comparison
| | PLC | SCADA | |---|---|---| | Primary role | Execute control logic | Supervise, log, alarm | | Runs the logic? | Yes — always | No — reads/writes tags | | Physical output wiring | Yes — I/O cards | None | | Scope | One machine / unit | Whole site or multiple sites | | Real-time response | 5–50 ms scan | Seconds polling interval | | Safety-critical? | Yes — directly | No | | Runs without operator | Yes | Yes — data logs unattended | | If it fails, machine… | Stops or faults | Keeps running (less visible) | | Programmed in… | Ladder, ST, FBD, IL, SFC | Configuration + scripting | | Typical hardware | Dedicated PLC rack | PC server + workstations |
Where They Connect
SCADA reads PLC data using an industrial communication protocol — EtherNet/IP for Allen-Bradley, PROFINET for Siemens, Modbus TCP for most other devices, or OPC UA as a vendor-neutral standard. The SCADA server has a driver that polls each PLC for tag values at a configured rate (often 1–5 seconds for display, faster for alarm detection).
The SCADA system maintains a tag database that mirrors the PLC tag database. An operator looking at the pump station screen on a SCADA workstation is seeing data that was polled from the pump skid PLC moments ago — not a live hardwired connection.
When an operator at the SCADA workstation changes a setpoint (say, adjusting a flow controller), SCADA writes the new value to the corresponding PLC tag. The PLC logic reads that tag and acts on it in the next scan. SCADA is always communicating through the PLC, never bypassing it.
Which One Do You Need First?
If you are starting a career in controls or automation: learn PLC programming first. The PLC is where the actual control logic lives. Every automation role — controls technician, automation engineer, commissioning technician — requires PLC skills. SCADA is the second layer you add after you understand what you are supervising.
If you already know PLCs and need to expand: SCADA adds historian, alarming, and multi-site supervision to your skill set. Ignition Maker Edition is free and a sensible starting point.
If a job posting lists both: they want someone who can wire up a PLC, write and troubleshoot ladder logic, AND configure SCADA tags and screens. Those are different skills but both are learnable.
Real Plant Examples
Water treatment plant: Dozens of pump stations across a catchment, each with its own Allen-Bradley CompactLogix PLC controlling the pumps locally. One Ignition SCADA server at the operations centre reads flow, level, and fault status from every station, logs the data to historian, and alerts the on-call technician if a pump faults. The pumps keep running when SCADA is offline — the local PLC logic handles start/stop based on level switches regardless.
Automotive assembly line: Each robot cell and conveyor section has a Siemens S7-1500 PLC. A FactoryTalk View SE SCADA system provides the shift supervisor with a plant-wide production dashboard, downtime tracking, and OEE reporting. The robot cells do not consult SCADA before each weld.
Oil and gas pipeline: RTUs (Remote Terminal Units) — essentially field-hardened PLCs — monitor pressure, temperature, and valve state at each station along hundreds of kilometres of pipeline. SCADA at the central control room provides the operator with a complete pipeline view, trending, and alarm management. The RTUs act autonomously on local logic if SCADA communication is lost.
Common Confusions Cleared Up
"SCADA controls the machines." SCADA supervises them. Control logic lives in the PLC. SCADA can send setpoints and commands to the PLC, but the PLC validates them against its logic before acting. If a safety interlock in the PLC prevents an action, a SCADA command cannot override it.
"You need SCADA before you can monitor a machine." Not at all. An HMI panel connected directly to the PLC provides machine-level monitoring without any SCADA server involved. SCADA becomes relevant when you need to aggregate many machines, log historical data, or monitor remotely.
"SCADA and HMI are the same thing." An HMI is typically a dedicated panel or screen for one machine, reading one PLC. SCADA is a server-based system connecting many PLCs and many operator workstations across a site. The boundary is blurring as software like Ignition can serve both roles, but conceptually they are different layers. See the PLC vs HMI post for the full breakdown of that layer.
Frequently Asked Questions
Q: Can SCADA work without a PLC?
A: SCADA can connect to any device that speaks an industrial protocol — RTUs, smart meters, DCS controllers — not only PLCs. But in most industrial automation, the PLC is the field device SCADA talks to. The two are not interchangeable; they occupy different layers.
Q: What is the difference between SCADA and DCS?
A: A DCS (Distributed Control System) is an integrated platform where both the control logic and the supervisory layer come from the same vendor (Emerson DeltaV, Honeywell Experion, ABB 800xA). SCADA is typically a supervisory software layer bolted on top of separate PLCs/RTUs from any vendor. DCS is more common in continuous process industries (chemicals, oil refining, power generation); SCADA + PLC is more common in discrete manufacturing and utilities.
Q: Does SCADA replace the PLC?
A: No. SCADA can write commands to PLCs, but it does not replace the real-time, safety-critical local control function. Removing the PLC would mean SCADA would need to respond to field signals and drive outputs directly — at network latency, with no deterministic scan. That is not safe for machine control. The PLC layer is always there.
Q: Which pays more, PLC or SCADA skills?
A: Both together pay more than either alone. PLC programming is the foundational skill with higher demand for entry-level roles. SCADA skills add salary leverage, especially in utilities (water, power, gas) and process industries where SCADA configuration and historian management are billable project work.
Ready to practise the PLC side of the equation? The motor start-stop scenario is free, runs in your browser, and auto-grades your ladder logic. No install, no hardware.