The PLC is the workhorse of industrial automation - the small, ruggedized computer that actually runs the control logic on a machine, skid, or process. If SCADA is the supervisory layer that watches and reports, the PLC is the layer that decides and acts in real time. This guide explains what a PLC is, how it works, how it differs from an RTU and a DCS, and where it sits in a modern SCADA stack.
A PLC (Programmable Logic Controller) in plain English: A Programmable Logic Controller is a ruggedized industrial computer that reads inputs from field sensors and switches, runs a control program, and drives outputs to devices like valves, pumps, and motors - reliably, in real time, in harsh environments.
A PLC continuously executes a control program in a fast, repeating loop called a scan: it reads all its inputs (pressures, temperatures, levels, switch states), solves the logic, and updates its outputs, typically in a few milliseconds. That deterministic scan is what makes a PLC different from an ordinary computer - it is built to respond within a guaranteed time, every time, which is what safety and process control demand.
Physically, a PLC is built to survive the plant floor and the oilfield: wide temperature ranges, vibration, dust, and electrical noise that would kill a normal PC. It connects to the physical world through I/O modules - discrete (on/off) and analog (4-20 mA, voltage) - wired to sensors and actuators.
PLCs are most often programmed in ladder logic, a graphical language that looks like an electrical relay diagram and was designed so electricians and controls technicians could read it. The IEC 61131-3 standard also defines function block diagram, structured text, and other languages for more complex logic. The program lives in the PLC and runs autonomously, so the process keeps operating even if the SCADA or network goes down.
Common PLC families in oil and gas include Allen-Bradley (Rockwell) ControlLogix and CompactLogix, and Siemens SIMATIC S7. Each speaks its own native protocol (EtherNet/IP for Allen-Bradley, S7comm for Siemens), which a SCADA platform must support to read the PLC's data.
In a SCADA architecture, PLCs are the field controllers. A SCADA platform polls the PLC over a protocol (Modbus, EtherNet/IP, OPC UA, Siemens S7), reads its tags, and presents them to operators - while the PLC keeps running the local control loop. On distributed oil and gas sites, a PLC or RTU at each wellsite or pad handles local logic and a cloud or on-premise SCADA aggregates the data.
This separation matters: the PLC provides real-time, safety-critical control that must not depend on the network, while SCADA provides visibility, alarming, history, and remote access on top. A monitoring platform like Merobix reads from your existing PLCs without changing their control logic.
A PLC excels at fast, discrete and analog control of machines and skids. An RTU is optimized for remote, geographically distributed sites with intermittent communications and low power - common in pipeline and upstream telemetry. A DCS is a plant-wide system of coordinated controllers built for large, continuous processes like refining. The lines blur - modern PLCs do telemetry and modern RTUs run logic - but the emphasis differs.
A PLC is a rugged industrial computer that reads sensor inputs, runs a control program, and switches outputs to devices like valves and pumps - in real time, reliably, in harsh conditions. It automates a machine or process locally.
A PLC runs the real-time control logic in the field; SCADA is the supervisory layer above it that collects data from many PLCs, shows it to operators, alarms, historizes, and enables remote access. The PLC decides and acts; SCADA watches and reports.
Most commonly ladder logic, a graphical language resembling relay diagrams. The IEC 61131-3 standard also defines function block diagram, structured text, sequential function chart, and instruction list.
It depends on the site. Fixed plants and skids typically use PLCs for fast local control; remote, distributed sites (wells, pipeline points) often use RTUs built for telemetry over marginal comms. Some sites use PLCs with telemetry features and skip a separate RTU.
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.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads Allen-Bradley, Siemens, and Modbus PLCs into a cloud or on-premise dashboard - without touching your control logic.