Well Pad Automation Architecture for Multi-Well Oilfield Pads

Quick Answer

A multi-well pad needs a layered architecture: field instruments and lift controllers at each well, a pad-level PLC or RTU for shared facilities (separator, heater treater, tanks, ESD), and a SCADA link (cellular, radio, or fiber) to the host. Standardize the bill of materials and logic templates so a two-person crew can commission a pad in a day instead of reinventing I/O maps for every lease. See the parent oilfield automation guide and Permian Basin automation for basin context.

Why single-well designs break on modern pads

Horizontal development concentrates 4–12 wells on one pad with shared production equipment. If each well is an island RTU with no pad controller, you cannot coordinate separator dumps, tank high-level shutdowns, or SIMOPS safely. If everything is hard-wired to one undersized panel with no spare I/O, the next well add-on becomes a field rewrite.

Recommended architecture layers

1. Well layer: Tubing/casing/flowline pressure, temperature, lift controller or VFD ( ESP, rod pump / POC, or gas lift), and local ESD where required.
2. Facility layer: Separator pressures and levels, heater treater temperature, oil/water tank levels, LACT or sales meter pulses, VRU or flare status, chemical pumps.
3. Pad controller: Typically Allen-Bradley CompactLogix or a rugged RTU ( SCADAPack) with room for expansion. Runs allocation-friendly totals, pad ESD, and protocol gateways.
4. Communications: Cellular LTE preferred; radio or satellite where coverage fails. One pad backhaul often serves all wells.
5. SCADA host: Ignition, Geo SCADA, or equivalent — pad overview, per-well detail, alarm management, historian.

Controller and I/O design choices

Use RTU vs PLC selection deliberately. PLCs win when pad logic, VFDs, and Ethernet/IP devices dominate. RTUs win on solar-powered, low-power, multi-protocol sites. Either way:

• Separate well I/O from facility I/O in the rack layout so add-on wells do not require ripping rewiring.
• Leave 20–30% spare analog and discrete capacity for the next wells on the pad.
• Put Class I Div 1/2 instruments and seals on the drawing, not as afterthoughts — see hazardous-area electrical practices.
• Keep life-safety / ESD independent of the SCADA WAN: local hardwired or safety logic must shut in if telemetry dies.

Allocation and shared facilities

Pad separators and tanks serve multiple wells. Automation should capture well test valves, dump counts, and meter totals so production accounting can attribute oil, gas, and water without clipboard math. Coordinate lift control with tank high-high and sales-line pressure so wells do not produce into a blocked system.

Standard packages beat custom every time

Large operators drill hundreds of wells a year. A standard pad automation package — panel layout, tagged I/O list, preloaded logic, commissioning checklist — cuts install time from days to hours and makes SCADA screens identical across the basin. Custom one-offs create orphan sites that only one tech understands.

Reference I/O budget

Pad controllers get undersized because designers count today's wells instead of the pad's final well count. Build the I/O budget from the permitted well slots, then add spare. These are planning figures — your instrument philosophy will shift them.

A six-well pad with two separators, a treater, and four tanks lands in the range where a small RTU runs out of room and a modular PLC chassis becomes the cheaper long-term answer — the core of the RTU versus PLC decision.

Network and protocol layout

Pads accumulate protocols. Plan the segmentation before the third vendor skid arrives with its own gateway.

Keep large register maps off the backhaul poll list. Let the pad controller poll the drives locally at speed and publish a curated tag set upward — otherwise cellular latency sets your control resolution.

Spare capacity and future wells

Pads grow. A pad built for four wells that later carries eight will either have spare I/O, spare panel space, and spare power, or it will get a second panel bolted beside the first with a different tag convention and a different technician who understands it. Reserve capacity on day one:

• Twenty to thirty percent spare analog and discrete points
• Physical DIN rail and wireway for added terminals
• Power and solar sizing headroom for added transmitters and radios
• Spare fiber or conduit path if wells will be added on the far side of the pad
• Tag numbering that extends cleanly to well 12 without renaming wells 1 through 4

SIMOPS and safety coordination

Concurrent drilling, completion, and production on one pad is the norm. Automation should support it explicitly: a documented ESD philosophy covering which wells and vessels shut in for which events, clear local isolation for crews working a specific well, and status indication that tells the control room what is producing versus what is under completion. Life-safety and high-high level functions belong in hardwired or safety-rated logic that survives a SCADA outage — the same principle that governs safety instrumented systems for oilfields.

Commissioning sequence that holds schedule

1. Power and grounding proven before any I/O checkout.
2. Point-to-point loop checks against the tagged I/O list, signed.
3. Lift controller communications verified per well, including register scaling.
4. Facility interlocks and ESD tested by simulation, documented.
5. Backhaul and host tags verified end to end, including stale-data detection.
6. Operator walkthrough and as-built markups before demobilization.

Skipping step two is the most common cause of a pad that "works" until the first real high-level event routes a dump valve to the wrong tank.

How NFM Consulting helps

NFM Consulting designs pad automation packages for Permian, Eagle Ford, and South Texas operators: CompactLogix and SCADAPack panels, ESP/POC integration, tank battery and separator I/O, cellular/radio backhaul, and host SCADA. Request an assessment or call (210) 405-4248.