A modern well pad is not a single well with a valve - it is a cluster of wells feeding shared separators, tanks, and injection equipment, and running all of it by hand would take a crew standing on site around the clock. Well pad automation is the layer of controllers, instruments, and logic that runs the routine operation of that pad on its own and reports it back to a central system. This guide explains what actually gets automated on a multi-well pad, how the pad's controllers make local decisions, and how they roll up into gathering-system SCADA to enable remote, lean-crew operation.
Well Pad Automation in one line: Well pad automation is the use of remote terminal units, edge controllers, instruments, and control logic to run the routine functions of a multi-well pad automatically and report them remotely. It typically covers separator level and dump control, plunger lift cycling, chemical injection, tank battery levels, and emergency shutdown, letting the pad operate without a person continuously on site. The pad's controllers roll up into gathering-system SCADA so operators can monitor and adjust many pads from a control room instead of touring each one.
The core of pad automation is separator control. A separator splits well fluids into gas, oil or condensate, and water, and its levels must be held within a band by dumping liquid out through control valves as it accumulates. Automating this means level instruments and a controller open and close the dump valves to keep each phase at its setpoint, rather than an operator watching a sight glass and cracking a valve by hand. This is the workhorse function on most pads because it runs constantly and directly determines whether the separator stays in balance.
Gas wells that no longer flow strongly on their own often use plunger lift, where a plunger cycles up and down the tubing to lift accumulated liquid off the bottom of the well so gas can flow. Automating plunger lift means a controller opens and closes the wellhead motor valve on a timed or sensor-driven cycle, adjusting the cycle to keep the well producing without loading up or venting excessively. Chemical injection is similarly automated: metering pumps dose corrosion inhibitor, scale inhibitor, methanol, or other chemicals at controlled rates, with the automation ensuring the dose tracks production rather than running blindly.
Around these, the pad automates its tank battery and its safety functions. Tank level instruments feed the automation so it knows when tanks are filling toward a high level that needs to be hauled or transferred, and overfill logic guards against spilling. The emergency shutdown system ties it all together: on a detected abnormal condition - high pressure, a fire or gas detection, a critical level - the ESD closes wellhead and process valves to bring the pad to a safe state automatically, without waiting for a human to react. Together these functions let the pad run its normal cycle, and protect itself, without continuous attendance.
The automation on a pad runs on local controllers - remote terminal units or edge controllers - that sit at the site and execute the control logic in real time. This local execution is essential because the pad's functions cannot wait on a round trip to a distant control room: a separator dump valve, a plunger lift cycle, and above all an emergency shutdown have to act on the instant, driven by the pad's own instruments and logic. The controller reads the pad's transmitters, runs the loops and sequences, and drives the valves and pumps directly, so the pad keeps operating correctly even if its communication link to the outside goes down.
Edge logic also lets the pad do more than execute simple loops. A modern pad controller can run the plunger lift optimization, coordinate the separator dumps with tank capacity, sequence a controlled shutdown and restart, and apply interlocks that prevent unsafe combinations of valve positions - all locally. The more capable the edge logic, the more of the pad's routine decision-making stays on site, which reduces how often a human has to intervene and makes the pad resilient to communication interruptions.
What the controller sends outward is the pad's state and the summary of what it is doing: current production, separator levels, tank levels, plunger cycles, injection rates, alarms, and shutdown status. It also accepts remote setpoints and commands, so an operator can adjust a plunger lift cycle, change an injection rate, or acknowledge and reset a shutdown without driving to the site. The controller is the boundary between the pad's fast local control and the operator's slower, supervisory oversight from afar.
A single automated pad is useful, but the value multiplies when many pads roll up into one gathering-system SCADA. Bringing each pad's controller into a common platform lets an operator watch the whole field - every pad's production, levels, injection, and alarms - from one place, and see them in the context of the gathering system and the central delivery point they feed. Because the pads are hydraulically connected through the gathering lines, seeing them together is also what lets the operator understand how a change at one point affects the rest.
A cloud SCADA such as Merobix reads the pad controllers over Modbus, DNP3, OPC UA, and MQTT and presents the field as a single system, so one operator monitors and adjusts many pads from a control room or a tablet rather than touring them. Setpoint changes flow back down to the pad controllers, so the operator can retune a plunger lift, adjust an injection rate, or acknowledge a shutdown remotely, while the pad's own edge logic continues to handle the fast, safety-critical control locally. The division of labor is clean: the pad runs itself, and SCADA gives the operator visibility and supervisory control over all of them at once.
This roll-up is what makes lean-crew, remote operation of a large field possible. Instead of staffing every pad, an operator watches the whole automated field centrally and dispatches personnel only where the data shows a real need - a pad whose production has fallen, a tank near hauling, a shutdown that needs a physical inspection before reset. Automation handles the routine, edge controllers keep each pad safe and running, and unified SCADA concentrates the field's visibility so a small team can operate what once needed many hands on the ground.
The common automated functions are separator level and dump control, plunger lift cycling on gas wells, chemical injection, tank battery level monitoring, and emergency shutdown. Together these let the pad run its routine production cycle - separating fluids, lifting liquids off gas wells, dosing chemicals, and managing tank levels - and protect itself against abnormal conditions, all without a person continuously on site.
The pad's control functions have to act instantly on the pad's own instruments - a separator dump, a plunger cycle, and especially an emergency shutdown cannot wait on a round trip to a distant control room. Running the logic on a local remote terminal unit or edge controller keeps that fast control on site, so the pad operates correctly and stays safe even if its communication link goes down. Central SCADA then provides supervisory visibility and setpoint changes on top of that local control.
Automation lets each pad run its routine cycle and protect itself without an operator present, while the pad's controller reports its state and accepts remote setpoints. When many pads roll up into one gathering-system SCADA, an operator can monitor them all and make adjustments from a control room or tablet, dispatching field crews only where the data shows a real need. This combination lets a small, lean crew operate a large field that would otherwise require staff at every site.
This page references the protocol specifications 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 your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.