Fixed routes leave the average lease operator at 25% value-added time. Exception-based surveillance lifts that to 60%. Pump-by-priority plus closed-loop scoring takes it past 90%. The approach is industry-validated. The barrier for small-to-mid operators is no longer evidence. It is adoption speed.
A Decade-Old Number Most Operators Have Not Acted On
In 2015 Alvarez & Marsal published a whitepaper that named the gap directly. Under traditional lease operating, roughly 25% of a lease operator's day is value-added work. Under exception-based surveillance (EBS), that figure rises to approximately 60%. The same crew, on the same wells, in the same trucks, recovers more than two hours per shift by routing on signal instead of schedule.
A&M went further. Where a traditional model assigns one lease operator per 20 wells, EBS can move that ratio to 30 or 40 wells per operator without sacrificing intervention quality. The math is durable. The work that disappears is the non-value-added rotation through wells that did not need a visit that day.
The whitepaper is ten years old. It has been peer-discussed at SPE. It has been cited in industry roundtables. And it has been productionized inside the supermajors. What has not happened, at scale, is small-to-mid operator adoption.
That is the gap worth naming on a Tuesday morning. The approach is not theoretical. The supermajors did not invent it for marketing. They built it because the math compounded for them. Independents are still running fixed routes because they believe the build is multi-year. It is not.
Three Operating Models, Same Crew, Same Wells
A field operation usually sits in one of three states. The difference between them is not headcount, equipment, or basin. The difference is how the day gets ranked.
State One: Fixed Routes. The pumper's route was set last quarter, or last year, or when the asset was last reorganized. Every well gets visited on cadence regardless of whether anything changed overnight. The 60-bopd well that started slipping at 2:14 AM is still scheduled for Thursday. The well that produced perfectly all week still gets Monday's hour. Roughly 25% of the shift goes to value-added work. The rest is windshield time, scheduled checks on wells that did not need them, and rework triggered by alarms the system never ranked.
State Two: Exception-Based Surveillance. The day is built around exceptions: wells outside their operating envelope, alarms that exceeded threshold, equipment showing early failure signatures. The pumper visits what changed. Routine wells are skipped. The shift moves from 25% value-added time toward 60%. This is the A&M number.
State Three: Pump-by-Priority with Closed-Loop Scoring. Exceptions are still the trigger, but the order is set by cash-flow impact, not alarm severity or recency. A 200-bopd well drifting 8% off forecast outranks a separator nuisance alarm even though the separator pinged louder. The day starts ranked. The crew runs the top of the list. Field observations from voice or tablet flow back into the score within minutes, not Tuesday. Value-added time approaches 90% because the operator stops doing low-margin work.
The three states are not philosophy. They are measurable in the data every operator already has. Time-on-site, miles driven, exception-to-visit time, deferred production caught per shift, mean time from anomaly to intervention. The spread between State One and State Three is the operating leverage the industry has been talking about since digital oilfield first showed up in a conference deck. The supermajors closed it. Most independents have not.
Want case studies and benchmarks like these?
For upstream + midstream operations leaders. Share your work email and our team will follow up with case studies, benchmarks, and what's changing in the field.
Three Levers, Three Citations the Buyer Respects
The supermajors did not move the metric with one technology. They stacked three operating levers on top of the underlying surveillance shift.
Preventative Maintenance. A&M's 2015 paper reported a 33% reduction in production downtime under EBS, driven by catching equipment degradation early enough to intervene at scheduled cost rather than emergency cost. Same crew. Same wells. Fewer pulls, fewer trucks, fewer 2 AM calls.
Closed-Loop Lift Control. In 2024, ExxonMobil and SLB presented at the SPE Artificial Lift Conference on a closed-loop optimization deployment across 1,300+ Permian wells. The reported uplift was 2% in oil production, with no equipment changes. The optimization was algorithmic. The wells were existing. The signal was already in the historian. (SPE Artificial Lift Conference, 2024.)
In the same year, ConocoPhillips published a JPT case study on a closed-loop deployment in the Montney, with reported production 3 to 4% above forecast, trending toward 6%. Chevron published a parallel case study in JPT on a Kaybob Duvernay deployment that delivered a 5% LOE reduction in year one. (JPT, 2024.)
Three operators. Three basins. Three independent peer-reviewed numbers. The pattern is the same: existing wells, existing instrumentation, an optimization layer that ranks the day.
Pump-by-Priority. The third lever ties the other two together. Ranking every potential field task by cash-flow impact and risk, not alarm volume or route order. WorkSync customers running pump-by-priority on the SCADA, EAM, and accounting stack they already own consistently report 15%+ cash flow uplift on the same well count. The math is the A&M math compounded by the SLB math, plus the layer that turns alarms into ranked work.
What the Gap Has Cost the Median Independent
Run the numbers on a 500-well operator producing 8,000 BOE/day net at $65/bbl realized. Annual revenue ballparks at $190M. A fixed-route operation at 25% value-added time is, by the A&M arithmetic, paying for three quarters of every lease-operator hour in non-value-added work.
Move that operator to State Two (60% value-added time) and the production impact is typically 2 to 4% from faster anomaly response alone. At 8,000 BOE/day, 3% recovery is 240 BOE/day. At $65, that is roughly $5.7M of annual revenue catch-up, before any OPEX reduction.
Move that operator to State Three (pump-by-priority with closed-loop scoring) and the documented uplift across deployments is 15%+ free cash flow on the same well count. At 8,000 BOE/day, that is in the range of $20M to $30M of annual cash flow, depending on price and basin. The same crew. The same wells. The same trucks. Different daily plan.
The number that matters to the operating committee is not the percentage. It is the absolute dollars left in the field every quarter under State One. The cost of waiting another year for the build that the supermajors finished a decade ago is roughly equal to the recoverable cash flow on a 30-day plan.
Why Most Independents Are Still on State One
Three reasons keep operators in fixed routes. None of them is the math.
One: The build looks multi-year. Internal IT projections for "implement EBS" historically arrived in years, not months. They assumed a SCADA refresh, a custom data warehouse, a system-of-record rebuild, and a multi-quarter integration program. Those projections were true in 2010. They are not true in 2026. The Work Engine reads the stack you already own. SCADA, Enertia, Quorum, AVEVA PI, Ignition, EAM, GIS. Read-only. One week to integrate.
Two: The vendor pitch usually starts with hardware. Most AI pitches still open on instrumentation gaps and edge gateways. That sequence puts the AI deployment behind a 6 to 18 month sensor refresh. The supermajors did not gate their EBS work on a sensor refresh. They scored what was there. So can independents.
Three: The pumper workflow looks fragile. Operators have been burned by tools that added handheld friction. The fix is voice-first capture and dispatch that the pumper does not have to learn. Willie, the field agent that runs on every visit, captures the observation and writes back to SCADA, EAM, and the scoring engine before the pumper finishes their coffee. The pumper does not change their workflow. The operation learns from every visit.
Strip those three friction points and the build is one week to integrate, one month to roll out, FCF impact the operator books this year.
What a 4-Week Adoption Pilot Actually Looks Like
The adoption pilot replaces the multi-year build with a 28-day loop, measured against a metric the operator's CFO would sign for if it moved.
Week 0. Baseline. Pick the metric. Deferred production, lifting cost per BOE, time from anomaly to dispatch, value-added time per shift. Date it. The number becomes the pilot acceptance criterion.
Weeks 1 to 2. Read-only integration into the existing stack. SCADA, accounting, EAM, GIS, historian, ERP write-back. No new sensors deployed. No new dashboards forced on the field. The connections sit underneath the systems the operation already runs.
Week 3. The scoring loop goes live. Every potential task is ranked overnight by cash-flow impact and risk. The ranked plan lands in every truck cab by 6 AM. Field observations flow back by voice. The dispatch board reflects the actual state of the field within minutes.
Week 4. Measure. Same metric, same wells, 28 days later. If it moved, the operator signs. If it did not, the operator walks. No license fee. No kill fee. No awkward sales call.
This is the loop the supermajors paid tuition on for a decade. The independents who run it now will not need to repeat that journey.
The Window Is the Next 18 Months
The competitive gap between operators on State One and operators on State Three is widening, not narrowing. Every quarter spent on fixed routes is a quarter of compounded deferred production, fragmented data capture, and reactive maintenance that the deployed reference operators are no longer absorbing.
The supermajors validated the approach. The consultants documented it. The peer-reviewed case studies are now public. What remains is adoption speed, and adoption speed is no longer the binding constraint it used to be. The operators who close the gap in the next 18 months will widen the spread on the operators who keep waiting for the perfect SCADA refresh.
The math is the same math A&M wrote down in 2015. The crew is the same crew the operator already has. The wells are the same wells. The difference is whether the day is ranked.
FAQ
Where does the 60% vs 25% number come from?
Alvarez & Marsal's 2015 whitepaper "The Advantages of Exception-Based Surveillance." The paper documented that under traditional lease operating models, roughly 25% of a lease operator's day is value-added work. Under EBS, that figure rises to approximately 60%. The numbers were measured across multiple operator deployments and have held up across a decade of subsequent industry application.
Are the supermajor case studies vendor-funded marketing or peer-reviewed?
The ExxonMobil case study was presented at the SPE Artificial Lift Conference in 2024 and is peer-reviewed in that venue. The ConocoPhillips and Chevron case studies were published in JPT (Journal of Petroleum Technology) in 2024, an SPE publication. JPT editorial vets case studies before publication. The numbers are sourced through a vendor, IOCaaS, but cited and discussed in the editorial frame, not in vendor marketing.
What is the difference between exception-based surveillance and pump-by-priority?
Exception-based surveillance triggers visits on alarms and deviations. Pump-by-priority adds a scoring layer: instead of treating every exception as comparable, each exception is ranked by cash-flow impact, risk, and crew availability. A separator nuisance alarm and a 200-bopd well drifting 8% off forecast both throw exceptions. Pump-by-priority ranks the second one first. The first is a 30-minute reset. The second is thousands of dollars a day of deferred production.
Can a small-to-mid operator really see results in 30 days?
Yes, on the metric the operator pre-commits to in Week 0. Material recovery typically begins within 30 days as ranked plans replace fixed routes and overnight scoring catches deferred production faster. Full closed-loop deployment, including optimized routing and nightly score-function retraining, completes inside 90 days. The deployed reference at a top 25 private producer covering 5,000+ wells across the Western Anadarko, Permian, and Wyoming achieved 15%+ free cash flow uplift on the same well count.
Does this approach require ripping out our existing SCADA or production accounting systems?
No. WorkSync reads SCADA, Enertia, Quorum, AVEVA PI, Ignition, EAM, GIS, and historian in read-only mode by default, with ERP and production accounting write-back optional. Operators on 15-year-old SCADA installations have deployed and moved the metric. The bigger lever is whether the data is reaching the score, not how new the historian is.
Why have most independents not already done this if the approach has been validated for a decade?
Three reasons, none of them economic. The internal IT build looked multi-year (it is not, anymore). The vendor pitch usually starts with a sensor refresh (it does not need to). And the pumper workflow looked fragile (it is not, with voice-first capture). Strip those three friction points and the build is one week to integrate and one month to roll out. The week-by-week shape of an actual 4-week pump-by-priority pilot is documented separately, including the Week-Zero metric, the Week-1 integration map, and the Week-4 measurement.
Start the 4-week pilot. Pick the metric Week 0. We run the scoring loop on the stack you already own. If the metric moves, you sign. If it does not, you walk away. No license fee.
Sources
- Alvarez & Marsal (2015). "The Advantages of Exception-Based Surveillance." Clevenger, Shannonhouse, Patterson.
- ExxonMobil and SLB. SPE Artificial Lift Conference, 2024. Permian closed-loop deployment, 1,300+ wells, 2% uplift, no equipment changes.
- ConocoPhillips. JPT, 2024. Montney IOCaaS case study, 3 to 4% above forecast, trending to 6%.
- Chevron. JPT, 2024. Kaybob Duvernay IOCaaS case study, 5% LOE reduction year one.
