Stand next to a rod pump that is fluid-pounding and you can feel it in your boots. The polished rod drops through an empty barrel, the beam jars, the whole unit shivers like a loose drive shaft. Ten thousand strokes of that a day is how a pumping unit eats itself alive. Rods stretch. Tubing wears through. Pump internals grind. And the motor is burning electricity to do it.
TL;DR. A pump-off controller (POC) senses when a rod pump is pumped off (pumping faster than the reservoir can supply fluid) and shuts the unit down until fluid recovers. The payback is rod life, motor life, tubing life, and power. On any rod-pumped well producing more than 5 to 10 barrels per day, a POC typically pays back inside a year. What a POC does not do is tell you how much was produced, what the tank level is, or what happened at the battery overnight. That is a separate layer of automation across the upstream operation, and on conventional wells where SCADA never penciled, it is where a SCADA alternative fits.
This is a plain-language guide to how POCs work in the field, why they matter, and where the operational-automation layer picks up where the POC leaves off.
What “Pumped Off” Actually Means
A rod pump lifts fluid from the bottom of the well using a reciprocating motion driven by the surface pumping unit. The pump has a standing valve (fixed) and a traveling valve (on the rods). On the upstroke, the traveling valve is closed and the pump lifts the fluid column. On the downstroke, the traveling valve opens and drops through the fluid.
A well is “pumped off” when the reservoir inflow cannot refill the pump barrel fast enough between strokes. The pump starts stroking partly-empty barrels, pounding fluid that isn’t there. That pounding: called fluid pound or gas pound: damages rods, tubing, pump internals, and the pumping unit itself. Left unchecked, it shortens equipment life dramatically.
The fix is simple: shut the pump down long enough for fluid to recover, then restart. That is what a POC does automatically, 24/7, without a pumper having to drive out.
How POCs Detect Pump-Off
Different POC technologies use different detection methods:
- Dynamometer-based (load cell): the POC measures the load on the rod string at each point in the stroke. A pumped-off stroke has a characteristic load curve showing loss of fluid load on the upstroke. Modern dyno cards can distinguish fluid pound from gas interference with high accuracy.
- Motor current / power: the POC monitors the motor’s current or power draw, which drops when the pump is lifting less fluid. Cheaper than a load cell but less precise.
- Time-based (legacy): older timer-based controllers simply run the pump for X minutes and off for Y minutes, without sensing actual well conditions. Still common on very low-rate wells where a cheap solution is fine.
- Vibration or sound: used occasionally on specific pump types. Less common in modern controllers.
The high-end POCs today are dynamometer-based with full stroke-by-stroke load analysis. Weatherford’s LOWIS, Lufkin’s SAM, and similar platforms can detect pump-off conditions within one or two strokes and either pause the unit or adjust stroke rate via a VSD.
Why POCs Pay Back
The math on a POC is rarely complicated:
- Rod life extension: rod strings in wells running fluid pound can fail 30–50% faster than those in well-controlled wells. A $20,000 rod job every 18 months vs every 30 months is a real savings.
- Tubing wear reduction: reduced pound means reduced tubing wear and fewer tubing jobs.
- Motor efficiency: a motor driving a pump with less-than-full barrels is doing work for nothing. Electricity savings on a well running 10+ hours a day add up.
- Pump intake wear: the pump internals last longer when they aren’t being fluid-pounded.
For any rod-pumped well producing more than 5 to 10 barrels per day, a POC typically returns its installed cost inside a year and keeps paying back for the life of the well. Even lower-rate wells benefit, though the payback period stretches.
What POCs Don’t Do
Within the oil and gas automation pillar, a POC is an equipment-level controller. It watches and protects one pumping unit. What it does not do:
- Tell the operator how much the well produced. The POC might know runtime and stroke count, but it doesn’t know tank levels, run tickets, or actual barrels sold.
- Log downtime reasons. A POC shutting down on pump-off is not a “problem,” but a POC shutting down on a power outage or a mechanical failure is. The POC’s shutdown log doesn’t always distinguish, and the operator has to piece together the story from the pumper’s visit.
- Feed the production report. Regulatory production reporting (Texas RRC Form PR, Oklahoma 300R, etc.) wants produced barrels and disposition, not stroke count.
- Coordinate across wells. A POC on well #1 and a POC on well #2 have no knowledge of each other.
Those gaps are where the operational automation layer comes in.
Solar-powered gateway. Installs in 10 minutes. Roughly 99% of SCADA's upside without the capex or the wiring. Scales from 50 wells to 5,000.
See how TinyPumper works →Amateur vs Pro: How Operators Pick and Deploy POCs
The operator who gets real payback from POCs isn’t the one with the fanciest dynamometer cards. They are the one who matches the controller to the well and actually reviews what the device is telling them.
| The amateur… | The pro… |
|---|---|
| Puts a timer-based POC on every well and calls it automation | Uses timers only on the lowest-rate wells and dyno-based POCs where fluid pound is a real failure driver |
| Sets the off-timer at install and never touches it | Reviews dyno cards or runtime data quarterly and retunes as the well declines |
| Buys the brand the service company pushed last quarter | Picks based on the detection method (load cell vs motor current) the well actually needs |
| Treats the POC shutdown log as noise | Correlates POC shutdowns with pumper visits to separate pump-off from mechanical trips |
| Leaves the POC running alone with no remote view | Pairs the POC with tank-level and pressure monitoring so one well’s pump-off doesn’t become a tank overfill downstream |
What To Avoid Before You Buy
- Buying a POC without fixing the underlying mechanical issue. A bent rod, a stuck traveling valve, or a worn pump barrel won’t be fixed by a controller. Diagnose first, automate second.
- The Orphaned-Controller trap. A POC that nobody looks at within 90 days of install becomes a box on a pump jack. Assign an owner before the PO goes out.
- The Paper Lag on a pump jack. A POC with cellular telemetry that dumps data into a vendor portal nobody opens is no better than a timer. The signal has to reach the pumper’s phone.
- Skipping the VSD question. On wells where inflow is variable, a pump-off-plus-VSD pairing usually beats pump-off alone. Ask the question before you spec the POC in isolation.
- Assuming the POC replaces the tank battery picture. It doesn’t. The POC watches one unit. The rest of the site still needs a view.
POCs and Pumper Workflow
On a well with a POC, the pumper’s visit changes. Instead of checking every well every day for pump-off conditions, the pumper can focus on:
- Tank gauges: beginning and ending inventory, temperature, BS&W.
- Run tickets: signed loads leaving the lease.
- Visual checks: packing leaks, hot bearings, unusual sounds, stuffing box condition.
- POC alarm review: anything the controller flagged that wasn’t normal pump-off behavior.
- Workover needs: wells that are pumped off more than usual signal a reservoir or mechanical issue worth investigating.
Capturing that pumper visit data in a consistent place is where operational automation picks up. GreaseBook is the pumper app most producers pair with POCs: the pumper logs the visit on a phone, the producer sees the data the same day, and POC alarm context gets tied to the well record rather than living in isolation on the controller. For the remote-monitoring side (tank levels, pressures, runtime between pumper visits) TinyPumper covers the conventional-well gap SCADA was too expensive to fill.
Producers who run clean POC programs don’t think of themselves as automation buyers. They think of themselves as stewards of the pumping unit. The POC is one tool. The pumper app is another. The tank battery monitor is another. All three serve the same job: keep the iron healthy, keep the barrels flowing, keep surprises off the morning call.
Wrong Fit for This Page
If you are researching pump jack kinematics, reservoir inflow theory, or designing a POC from scratch, this page is too practical for your purposes. This page is written for the producer who wants to understand what a POC does in the field, when it pays back, and how it fits into the broader data chain, regardless of whether company pumpers or a contract pumping outfit work the route.
FAQ
Can TinyPumper replace a pump-off controller?
No. A POC is a hardware device that runs control logic at the pump jack. TinyPumper is a separate piece of hardware: a solar-powered gateway with radar and pressure sensors that watches tank levels, pressures, and compressor and engine runtime. They solve different problems and work together. TinyPumper covers the remote-monitoring piece SCADA would normally handle on a conventional well where SCADA was too expensive to install or is no longer worth maintaining.
What is a pump-off controller?
A pump-off controller is an automation device that monitors a rod-pumped well and shuts down the pumping unit when the well is pumped off (pumping faster than reservoir inflow). After a programmed off-time, the POC restarts the unit.
How much does a pump-off controller cost?
POC installed costs vary widely. Basic timer-based controllers can run a few hundred dollars plus installation. High-end dynamometer-based controllers with cellular telemetry can run several thousand dollars installed. On a typical pumping well, payback is usually under a year.
Do all rod pump wells need a POC?
Almost all meaningful-rate pumping wells benefit from a POC. Very low-rate wells (under a few barrels per day) may run continuously or on a simple timer, where the payback is thinner but still positive.
What is the difference between a POC and a VFD?
A POC senses pump-off conditions and shuts down or cycles the pumping unit. A variable frequency drive (VFD) or variable speed drive (VSD) adjusts the pumping unit’s stroke rate continuously to match reservoir inflow. Many modern setups pair a POC with a VSD for tighter control.
Related Pages
- Oil and gas automation: the pillar guide to automation in the industry.
- Oilfield automation: the field-level view of automation at the wellsite.
- Wellsite automation: what automation at the well pad actually includes.
- Automation in oil and gas industry: the layered automation stack explained.
TinyPumper is the SCADA alternative that watches the rest of the site (tanks, pressures, compressor runtime) over cellular or satellite, from a matchbox-sized gateway that installs in 10 minutes. Knowing the pump kicked off is useless if the tank filled up overnight and nobody saw it.
See how TinyPumper fits alongside a POC →