Skip to main content
Aerial view of a service truck crossing a vast oil field
Back to Insights
The ApproachSEO Guide

Pumper Route Optimization: From Fixed Loops to AI-Prioritized Field Plans

Route optimization is not just about GPS. It starts with knowing which wells to visit in the first place.

Michael Atkin, P.EngMarch 30, 202610 min read

Most lease operators in upstream oil and gas drive the same route every day. They visit the same 15-20 well pads, in the same order, regardless of which wells actually need attention. The route was set months or years ago based on geographic convenience, and it rarely changes unless a well goes down hard enough to force a deviation.

This is not a technology problem. It is a prioritization problem. No one has told the operator which wells matter most today.

The Real Cost of Fixed Routes

A typical lease operator in a Permian or Mid-Continent basin covers 150-250 miles per day across 15-20 sites. At roughly 20-30 minutes per site (drive time plus on-site time), that consumes a full 10-hour shift. Every site gets roughly equal time regardless of whether it needs five minutes of visual inspection or two hours of troubleshooting.

The hidden cost is not the fuel or the truck wear. It is the opportunity cost. While the operator spends 30 minutes at a well producing normally, three wells on the other end of the field are losing production. A rod pump is showing intermittent failures. An ESP is drawing abnormal amps. A separator is running above setpoint.

These issues were flagged in SCADA overnight, but the operator will not reach those wells until tomorrow's route brings them around. By then, the rod pump may have failed completely (turning a $500 adjustment into a $12,000 pull-and-replace), and the separator issue may have caused a gauge run error that takes two weeks to reconcile in production accounting.

Field superintendents know this dynamic intimately. They spend the first hour of every morning triaging calls, reviewing overnight alarms, and trying to reprioritize the day. But with 200+ SCADA alarms and no economic ranking, the best they can do is identify the most obvious emergencies. The slower-burning losses (gradual production decline, intermittent equipment issues, wells producing below forecast) stay invisible until the monthly report.

Why GPS Routing Alone Does Not Solve This

Several fleet management and logistics platforms offer route optimization for field operations. These tools find the shortest or fastest path between a set of predetermined stops. They solve the traveling salesman problem.

But they start with the wrong assumption: that the set of stops is correct.

If a lease operator's route includes eight wells that need nothing and excludes four wells that are losing production, finding the optimal path between those eight wells does not help. You have optimized the wrong work.

True route optimization for field operations requires two steps:

  1. Decide which wells belong on today's route based on real-time operational data, economic scoring, and predicted equipment health.
  2. Sequence those wells to minimize drive time while respecting priority order and time constraints.

Step one is the hard part. It requires integrating SCADA data, production accounting, CMMS history, and engineering models into a single scoring engine that evaluates every well every night. Step two is straightforward once you know which wells matter.

Get the WorkSync Field Ops Brief

Monthly read for upstream + midstream operations leaders. Case studies, benchmarks, and what's changing in the field. Unsubscribe anytime.

What Intelligent Route Optimization Looks Like

Here is what a WorkSync-powered morning looks like for a lease operator in the Western Anadarko Basin:

5:45 AM: The operator opens the WorkSync app on their phone. Today's plan shows 12 stops, not the usual 18. Three low-priority wells (producing normally, no flags) have been dropped. Four new stops have been added based on overnight ML anomaly detection.

Stop 1 is a rod pump well producing 22 BOE/day that showed an abnormal polished rod load pattern overnight. Estimated production at risk: $1,800/week. The app shows the specific anomaly, the well's recent production trend, and the recommended inspection steps.

Stop 4 is a gas lift well where the injection rate has been trending away from the optimal curve for three days. Before WorkSync, this would not have been caught until the next engineering review cycle (two weeks out). Estimated impact: 8 BOE/day deferred production.

Stop 8 has been flagged as a safety priority: a high-pressure alarm on a vessel that requires a physical inspection per the operator's safety protocols. This stop was moved up in the route sequence to ensure it gets addressed before the crew runs out of daylight.

The route between stops is optimized for geography and priority. High-value stops are front-loaded so that if the day runs long, the lowest-impact work gets deferred to tomorrow (not the other way around).

4:00 PM: The operator has completed 11 of 12 stops. The one deferred stop was a routine visual check on a well with no active flags. Total miles driven: 140 (vs. the usual 210). Total estimated value of work completed: $14,200 in production protected or restored.

How WorkSync Makes This Work

WorkSync's OPS platform runs the scoring and routing engine that powers this workflow:

Overnight scoring: ML models evaluate every well against its learned operating baseline. Deviations are flagged, categorized by type (production, equipment, safety, compliance), and scored by estimated economic impact.

Morning plan generation: By 6 AM, every crew has a ranked task list and an optimized route. The superintendent reviews the plan in the Control Room and can adjust priorities before crews depart.

Real-time adaptation: If conditions change during the day (a new high-priority alarm, a well that took longer than expected), the system can re-optimize the remaining route.

Closed-loop feedback: Every completed task feeds back into the model. Did the rod pump issue resolve after the adjustment? Did production recover? This data improves future scoring and reduces false positives over time.

In the Western Anadarko deployment, operators using WorkSync saw 35% fewer site visits with higher task completion rates and measurably better production outcomes. Lease operators reported that their days felt more purposeful because they understood why each stop mattered.

Want to see what optimized routes look like for your field? Request a walkthrough or explore the 6 AM plan.

Frequently Asked

What is pumper route optimization?

Pumper route optimization uses AI to determine which wells a lease operator should visit each day, in what order, based on production impact, equipment health, safety flags, and geographic proximity. Unlike traditional GPS routing that just finds the shortest path between fixed stops, intelligent route optimization starts by deciding which stops matter most.

How is agentic route optimization different from GPS routing?

GPS routing finds the shortest path between predetermined stops. Agentic route optimization decides which stops belong on the route in the first place by scoring every well by economic impact, then sequences them to minimize drive time. A pumper might skip three low-priority wells and gain 90 minutes for a high-value remediation that saves $8,000 in deferred production.

How much drive time can route optimization save?

Operators using WorkSync have seen a 35% reduction in site visits with higher task completion rates. By eliminating low-priority stops and sequencing high-value work geographically, lease operators typically reduce daily windshield time by 60-90 minutes while completing more valuable work.

What data does agentic route optimization need?

Effective route optimization requires SCADA data (pressures, flow rates, temperatures), production accounting data, equipment maintenance history from CMMS, and GPS/telematics data from field vehicles. WorkSync integrates with 40+ systems to build a complete operational picture.

See ranked routes for your field

See how WorkSync can transform your operations.

Related Insights

Wellhead operations crew in the field, the deployment surface for a pump-by-priority pilot
The Approach

The 4-Week Pump-by-Priority Pilot: What Actually Happens, Week by Week

Most operators expect a multi-quarter build. The shape of an actual pump-by-priority pilot is one week to integrate read-only onto the existing stack, two weeks to put a ranked plan in every truck cab, and one week to measure against a metric the controller signed on Day Zero.

Crude storage tanks at a battery, the surface area for fill-rate-driven tank gauging
The Approach

When, Not Which Day: Cutting Tank Gauging in Half Without Adding Sensors

The lift in tank gauging is not in the gauging. It is in the cadence. Gauging cadence built around a 3-day route is a holdover from an era when no one could predict tank level overnight. The forecast has been on most operator stacks for a decade. Small-to-mid operators have not adopted because they think the build needs new sensors. It does not.

Field operator capturing observations on a tablet at a wellsite, the data already in the operation
The Approach

You Don't Need More Sensors. You Need a Better Question.

Most AI pitches in oil and gas start with a telemetry refresh. Wrong order. The data is already there. Nobody is scoring it. How to deploy AI on the SCADA, accounting, and EAM stack you already own, without buying a single new field-side sensor.

Aerial view of oil field at dawn
The Approach

6:00 AM Clarity: How AI-Driven Route Optimization Changes the Shape of a Field Day

Walk through what a day looks like for a lease operator before and after Work Engine, from legal pads to optimized routes by 6 AM.

Aerial view of field truck traversing vast operational area
The Approach

18 of the Right Sites Is Better Than 26 of the Wrong Ones

The assumption was that field crews were spending too much time at each location. The data showed the opposite. They were rushing through sites, skipping completable work, and driving to the next location out of instinct, not necessity.

Multiple pumpjacks operating across an upstream lease, the deployed reference for exception-based surveillance at scale
The Proof

60% vs 25%: The Field Productivity Gap the Supermajors Already Closed

A&M, ExxonMobil, ConocoPhillips, and Chevron all documented the same operating model. Three peer-reviewed citations, three operating levers, one durable conclusion: the approach is validated, the gap for small-to-mid operators is adoption speed.