What Is a Gathering System?

Back to Blog

Where the Gathering System Fits

Individual wells produce at modest, variable pressures and rates, and they are scattered across a lease or basin. A gathering system aggregates all of that flow so it can be measured, separated, treated, and compressed efficiently at central facilities rather than at every wellhead. Gas gathering lines carry raw wet gas from pads to a gas plant; oil gathering lines move crude from lease batteries to a central tank facility or LACT point; water gathering lines route produced water to disposal.

Because wells decline and pipeline pressure must be managed, gathering systems usually include field compression to boost low-pressure gas, plus separators, dehydration, and measurement at key nodes. The layout is often a radial or trunk-and-lateral pattern feeding one or more central delivery points.

Measurement and Monitoring

Every well or pad entering a gathering system typically has a meter (orifice, turbine, ultrasonic, or Coriolis) so production can be allocated back to the correct lease and royalty owner. Pressure and flow are monitored throughout the system because a rising line pressure can back production off a well, while a sudden pressure drop can indicate a leak or line break.

Gathering systems are geographically spread and often unmanned, which makes them a classic SCADA application. RTUs and flow computers at wellheads, compressor stations, and delivery points report pressure, flow, temperature, and equipment status back to a central system. A cloud-native SCADA platform can poll those field devices over Modbus, DNP3, or MQTT to give operators a single live view of the whole gathering network, trend line pack, and alarm on abnormal pressure profiles that hint at a blockage or leak.

Pressure Management Across the Network

The gathering system's operating pressure is a shared resource. Every well on a lateral delivers into the same line pressure, so a single high-rate well coming online, a compressor trip, or a choked plant inlet raises backpressure on all of its neighbors and backs their production off at once. Operating the network means constantly balancing what the wells can deliver against what the pipe and compression can take away, and the trend that matters most is the pressure profile along the whole system, not any single gauge at any single site.

That balance shifts over the life of the field. Wells decline, so the line pressure the system must hold has to fall over time, which is why compression gets added in stages and why laterals get looped or re-routed as basins mature. A line pressure that was fine at first production can become the single biggest constraint on output years later, and identifying which segment is the bottleneck is a trending exercise across many points at once - a natural job for the SCADA build described in gas gathering system monitoring.

Liquids, Hydrates, and Pigging

Raw gas leaves the pad wet, and the gathering line is where liquids fall out. Condensate and water collect at low points, increasing pressure drop and eventually slugging forward into compressor stations and the plant inlet. Operators manage this with a pigging program: launchers and receivers at intervals along the line, and regular runs that sweep accumulated liquids ahead of the pig. Rising differential pressure across a segment between pig runs is the classic signature of liquid loading, which is one more argument for instrumenting pressure at both ends of major segments.

Cold weather adds hydrates and freeze-offs. Wherever wet gas takes a sharp pressure drop - across a choke, a control valve, or an orifice - the gas cools, and hydrates can form and block the line entirely. Sites mitigate per local practice with methanol injection, line heaters, insulation, or drip pots, and operations watch pressure differentials closely in cold snaps because a freeze-off looks exactly like a valve someone quietly closed. Where and how to treat is a site-specific engineering decision; the monitoring pattern, watching for sudden divergence between adjacent pressures, is universal.

A Point List for a Gathering SCADA Build

When you scope telemetry for a gathering network, the points group naturally by node type:

Node	Points worth bringing back
Well pad	Tubing and casing pressure, line pressure, flow, separator dump status, ESD status
Compressor station	Suction and discharge pressure, run status, alarm and shutdown cause
Pig launcher / receiver	Barrel pressure, pig passage indication, valve positions
Central delivery point	Custody or allocation flow, pressure, temperature, gas quality where measured
Liquids handling	Tank levels and haul-off status at the tank battery or LACT unit

The list is deliberately biased toward pressures. Pressure is the cheapest, most reliable signal on a gathering system, and nearly every failure mode - leak, blockage, freeze-off, compressor trip, closed valve - shows up first as adjacent pressures diverging from their normal relationship to each other. Flows allocate production and confirm the story; pressures tell it first, which is why experienced gathering operators read the pressure profile the way a doctor reads vital signs. Start the point list with pressures at every node, then add flow, status, and quality points as budget and comms capacity allow.

Frequently Asked Questions