WellOPS Production Surveillance
Production Surveillance Is End to End or It Is Theater.
Most operators run production monitoring and call it surveillance. The difference is five elements: detect, score, route, execute, learn. WellOPS runs the full loop on the SCADA, historian, accounting, and EAM stack you already own, and puts a ranked, dollar-denominated plan in every truck cab by 6 AM.
The Word Migrated. The Action Half Fell Off.
Production surveillance is a phrase the industry has used since the late 1980s. It came out of the major-IOC field-of-the-future programs that put control rooms behind every offshore complex. In that context the term meant something specific: a small team of engineers, sitting in a centralized room, watching live signal from a producing asset, and intervening when the signal said to intervene. That room has an onshore descendant, and independents run it today as a remote operations center.
By the mid-2010s a dashboard built on top of a historian was calling itself the same thing. By 2026 the term covers any software that displays a production number on a screen. The action half of the original definition quietly fell off. The watching half got rebranded as “real-time visibility.”
The result is that most independent operators describe themselves as running production surveillance and run nothing of the kind. They run production monitoring. The two words look similar. They do completely different things to free cash flow.
Run end to end, production surveillance is management by exception applied to producing wells: watch every well continuously, act only where the deviation pays. The oilfield’s own name for the first half of that, and the reason it plateaus once the queue grows, is covered in the guide to pump by exception and its ceiling.
The Five Elements of Real Production Surveillance
The complete definition runs end to end. Five elements, each of which has to actually happen. Drop any one and the loop opens. The cash flow leaks out the gap.
1. Detect
Live signal from SCADA, well tests, run tickets, deferment data, inspections, and route history is read continuously. ML models calibrated to each well's normal behavior catch deviations the static-threshold alarm misses. Most operators have this. It is necessary and far from sufficient.
2. Score
Every detected anomaly is scored in dollars, not in alarm severity. Production at risk, working interest, lifting cost, commodity strip, deferment risk. A stuck valve on a 5 BOPD stripper at $60 oil scores below a failing rod pump on a 200 BOPD producer at $80 oil. The output is a ranked list denominated in cash flow.
3. Route
The scored anomaly is sequenced against the crew roster, qualified by skill match and equipment dependency, bounded by hours of service, and assigned. A constraint-aware optimizer turns the ranked list into an executable plan, not a suggestion.
4. Execute
The work lands in the truck cab on a mobile surface the pumper actually uses. The Willie voice agent runs the JSA. The form fills itself from SCADA and the last shift. The operator confirms what is true. Outcome is captured against the originating anomaly.
5. Learn
The outcome feeds back into the detection model and the scoring model overnight. Tomorrow's plan reflects what the field did yesterday. False alarms drop. Ranking accuracy compounds. The system is measurably better next quarter than it is today.
If any one of those five is missing, the result is not production surveillance. It is one of the four partial states most operators are in today: monitoring without ranking, ranking without routing, routing without execution feedback, or execution without learning. Each partial state leaves a measurable fraction of the cash flow in the field.
Where Most Operators Actually Sit on the Loop
The honest assessment that comes out of the 24-hour AI operations diagnostic puts most independents somewhere on the same five-stop maturity ladder. The pattern is consistent enough to be useful.
- ●Stop 1 only. SCADA alarming on threshold breaches. No central screen, no consolidated plan. Fixed routes regardless of overnight changes.
- ●Stops 1 to 2. Most independents. SCADA plus a historian-based dashboard plus a 7 AM flash report. Route still gets cut against habit and proximity.
- ●Stops 1 to 3. Detection and scoring in place. Ranked list lives in a dashboard or daily report. Execution still set by the foreman texting at 5:30 AM.
- ●Stops 1 to 4. Ranked plan sequenced and delivered in cab. Work gets done. Outcome not captured back into the model, so the system never learns.
- ●Stops 1 to 5. The supermajors and the top quartile of Lower-48 independents. The full loop runs nightly. The 15 to 18 percent operating delta lands here.
The operating delta between the top quartile and everyone else, measured at the free cash flow line, is the gap now showing up at every RBL redetermination cycle and PE term sheet. The supermajors are naming the loop on earnings calls. The independents who close the gap this year compound. The ones who wait keep paying the deferment tax and keep watching their pilots stall.
Dashboard vs. Pump by Exception vs. WellOPS Production Surveillance
Three things the industry uses the word “surveillance” for, side by side, by what they actually deliver to the day of the shift.
| SCADA Dashboard | Pump by Exception | WellOPS Production Surveillance | |
|---|---|---|---|
| What it does | Displays live production data on a screen | Dispatches a crew when an alarm trips | Runs the full detect, score, route, execute, learn loop |
| Where the loop stops | Detect (element 1) | Detect + partial Execute (elements 1 and 4) | Closed end to end |
| Day-of-shift output | A wall of trends and a list of alarms | A list of alarms, treated as equally urgent | Ranked, dollar-denominated daily plan in every truck cab by 6 AM |
| Field-team behavior change | Foreman reads the dashboard, texts the crew | Crew reacts to alarms in proximity order | Field works the highest-value task first, by default |
| Closed learning | None. Same alarm fires the same way next quarter | None. Static rules, manual tuning | Yes. Nightly model retraining on captured outcomes |
| Free cash flow impact | ~0 measured against monitoring baseline | Fewer unnecessary visits, gains erode with alarm fatigue | 15%+ FCF uplift on the same well count (5,000+ well reference) |
| Buyer signal | Era 1 to Era 2 on the maturity ladder | Era 2 on the maturity ladder | Era 4 on the maturity ladder |
Why WellOPS Production Surveillance Is the Version You Can Buy This Quarter
WellOPS runs production surveillance end to end. Detection on top of the SCADA, well test, run ticket, and deferment data the operator already runs. Scoring on the operator’s actual economics, not alarm severity. Routing against the crew roster, the skill matrix, the equipment dependencies, and the geography. Execution in the truck cab through the Field Data Capture surface and the Willie voice agent, so the pumper does not type a form at the end of a long shift. Learning that runs nightly so the next morning’s plan reflects what the field did yesterday.
The deployment shape mirrors the four-week pump-by-priority pilot. Week one to integrate read-only through the DataHub over the existing stack. Weeks two and three to put the ranked plan in the cab. Week four to measure against a metric the controller signs for on day zero. Pricing is below VP signing authority on the entry tier. The Impact Guarantee carries the financial risk: if the metric does not move past the threshold, the operator walks away with the integration documentation and the baseline dataset. No license fee. No kill fee.
The architecture is the same shape on a 200-well operation as on the 5,000-plus-well, three-basin deployed reference at a top 25 private producer across the Western Anadarko, Permian, and Wyoming. The closed loop scales because it was designed as a closed loop, not as a dashboard that grew downstream attachments.
Production Surveillance FAQ
Frequently Asked Questions
Keep Reading
Related Resources
Dive deeper into how WorkSync transforms operations.
33% of Production Downtime Is Preventable
The A&M-published benchmark behind exception-based surveillance, and the four-week adoption path.
Read more →Deferred Production
How overnight detection catches deferred production, the first element of the loop.
Read more →Exception-Based Surveillance
The supermajor playbook the independents still do not run, and what it takes to adopt it in four weeks.
Read more →Pump by Priority
The economic-ranking element of the loop, scored in dollars not alarm severity.
Read more →Pump by Exception
Where the industry started. Why it stops one element short of a complete loop.
Read more →WellOPS
The field operations product that runs Production Surveillance end to end, with Willie riding shotgun.
Read more →The 4-Week Pump-by-Priority Pilot
What actually happens, week by week, including the Impact Guarantee clause.
Read more →Run the full loop on your data. See it in four weeks.
WellOPS Production Surveillance runs detect, score, route, execute, learn on the systems you already own. Ranked plan in every truck cab by 6 AM. Impact Guarantee in writing.