WellOPS · Route Optimizer · Crew Dispatch

Not the shortest route. The most profitable one.

Route Optimizer maximizes the impact of your team.

See Your Wells Ranked View a Sample 6 AM Plan

For Field Superintendents · Dispatch · Operations Managers

Part of WellOPS

It plans on value density, dollars of production impact per crew-hour, and builds the day that captures the most value the field can physically execute under crew qualifications, site access windows, hours of service and co-routed equipment.

35% fewer miles driven for the same production coverage, measured across 5,000+ wells in live deployments.

You buy WellOPS by WorkSync. Route Optimizer is the route optimization capability of WellOPS, the operating platform for production operations, and it ships with the platform.

What the module does

A lease operator's day is not a delivery route

Route Optimizer solves a harder problem than a delivery router does.

Six classes of work, each with its own windows

A lease operator’s day mixes six classes of work (scheduled maintenance, failure response, regulatory deadlines, risk-based visits, liquid management, routine gauging), each with its own time windows, qualification requirements, and cost of deferral.

The stops interact: a hauler dispatched late shuts in a well; an inspection missed by an hour erases a month of capture credit. Generic fleet routing has no way to see any of that.

The deeper difference is the objective.

Delivery routing minimizes distance because every stop is worth the same. In the oilfield, stops differ in value by orders of magnitude on the same day: a failing pump on a high-rate producer against a routine gauge on a stripper.

A solver that minimizes miles first is optimizing the wrong number, which is why Route Optimizer scores before it sequences.

Category guide

This page covers the WellOPS module. For the buyer's guide to the category, including how oilfield routing differs from delivery routing and five questions to ask any vendor, start with route planning software for oil and gas.

The WellOPS route view: the day’s open sites in route order with their flags and BOE, $4,573 at risk today, beside the numbered stops on the site location map (synthetic demo data) — Demo screen, synthetic data

WellOPS on a phone: today’s route with the first stop open, why the crew is there, and the do-this-now task with its one-tap outcomes (synthetic demo data) — Demo screen, synthetic data

Value density beats the shortest path

Route Optimizer plans around value density: dollars of production impact per crew-hour, not miles per stop.

35%
Fewer miles driven, same production coverage, deployment figure
15%
FCF uplift on the same crew, deployment figure
5,000+
Wells, measured in live deployments
4 wk
To crews live, the standard rollout cadence

How the solver builds the day

Each candidate stop carries the economic score from the ranked work plan. The solver then builds the day that captures the most value the field can physically execute, subject to qualifications, time windows, and hours of service.

The shortest route and the most profitable route are rarely the same day; the difference between them is what fixed loops leave on the table.

The result, measured across 5,000+ wells in live deployments: 35% fewer miles driven at equal economic coverage, because crews stop driving to low-value stops out of habit.

Operators who follow that logic all the way stop maintaining standing routes entirely and run sensor-driven dispatch instead of a route sheet.

The guides and the calculator

The category-level treatment of that trade, including the constraint reality and the dispatch decision behind it, is in the guide to oilfield route planning and dispatch. The dollar economics are modeled on the route economics calculator, the operator-level playbook lives at lease operator and pumper routes, and the ranking that feeds the solver is pump by priority.

A gravel lease road leading to a small well pad with two tanks and separators on open prairie at dusk, trees either side of the road and a cloud bank catching the last light — The lease road to a single pad on open prairie, at dusk

How the day gets solved

One objective, six binding constraints.

The objective is value captured per crew-day. Everything below is a hard bound the solver works inside, which is why the output is a day a crew can actually run rather than a wish list sorted by dollars.

Qualifications

H2S-certified crews to sour wells, pressure-vessel inspectors to PV assets, electrical work to electricians. An unqualified crew never sees the stop, so the constraint holds before the audit rather than after it.

Time windows

Site access hours, landowner and surface-use restrictions, regulatory inspection windows, and the windows on other people the job depends on, such as a hauler or a third-party inspector.

Hours of service and shift shape

Shift length, mandatory breaks, yard start and yard end, and travel to the first site. No crew is assigned more than it can safely complete, which is what keeps a value-maximizing plan from becoming an unsafe one.

Equipment co-routing

Jobs that need a pulling unit, a hot oil truck, a vac truck or a specific tool get that equipment scheduled to arrive with the qualified crew, rather than a crew arriving to a job it cannot start.

Drive time on real roads

Travel is estimated on the road network and on your own traversal history, because no public feed covers private lease roads. Your crews driving the leases is the data that makes the estimates true.

Value density, the objective

Each candidate stop carries its economic score from the ranked work plan. The solver maximizes dollars of production impact per crew-hour, which is why the shortest route and the most profitable route are rarely the same day.

And when the day changes

The 6 AM plan is a forecast, so it re-solves within limits.

Re-optimization fires on a defined trigger set: a well down, a higher-value flag, a crew or vehicle out, a weather event, a hauler slipping. It pushes only to affected crews, behind a minimum-improvement bar so small re-orderings are not worth the cognitive cost of a changed plan, and in-progress work is interrupted only by a safety gate. Every override a field team member makes is one tap with a reason code, and that reason is recorded as data, because a stop the field consistently pulls forward is carrying information the scoring has not captured yet.

The whole field, one plan

Every route, drawn where the value is.

Fleet view: each dashed line is one crew's day, threaded through the open flags, and each flag is drawn at the size of what it is worth. Not the shortest route. The most profitable one.

Critical flags reached: 5 of 5
Value reached: $34,214/d
Drive, 375 mi: $1,031
Net of the drive: $33,183/d

Against nearest-first: 2 more critical flags reached, $7,852/d more net of the drive, for 206 more miles. The drive is spent where the value is.

Crew A7 stops2h 39m drive$10,331/d

Crew B6 stops2h 28m drive$7,926/d

Crew C6 stops2h 39m drive$9,415/d

Crew D6 stops2h 58m drive$6,542/d

Critical flag, sized by $/day
High flag, sized by $/day
Medium flag, sized by $/day
Well, no open flag
Crew yard

46 open flags across 148 wells; 25 of them make today’s routes, and the rest wait for a day they are worth the drive. The crew ledger is the value plan. Synthetic demo data, generated. No customer data, no real geography, no real operator.

How the shortest drive is drawn

Shortest drive gives each crew the same number of stops from the same yard, always taking the nearest open flag next, and prices what it reaches on the same ruler. Drive is costed at the demo crew rate. The deployment’s 35% fewer miles is measured against fixed-route habits, not against this nearest-first comparison.

What it does

6 capabilities that turn your existing stack into action.

Multi-stop optimization across a crew's whole day

A constraint-based solver assembles stops into a coherent route, formalized as a multi-class vehicle routing problem with synchronization constraints. It factors site access windows, yard start and end, vehicle capacity, and turnaround time.

Crew qualifications enforced in the route

H2S-certified crews routed to sour wells. Pressure-vessel inspectors routed to PV assets. Unqualified crews never see the stop in their plan. No post-hoc audit failures.

Ranked work priority drives sequencing

Pulls from Work Engine's economic ranking. High-impact tasks scheduled first in the crew-day; low-impact backfill fills gaps. Priority can re-rank mid-shift if conditions change.

Real-time re-optimization when conditions change

Weather event, vehicle breakdown, new high-priority alert, remaining stops re-assigned across all crews without a call to dispatch. Continuous optimization, not a once-a-morning batch.

Mobile-first, offline-capable

Plans delivered to truck cabs via mobile. Cached offline for cellular-dead zones. Field completion feeds back into the ranking for tomorrow's plan.

Hours of service and equipment co-routing respected

Shift length, mandatory breaks, and travel-to-first-site time are built into every plan; no crew is assigned more than it can safely complete. Tasks that need a pulling unit or a hot oil truck get the equipment co-routed with the qualified crew.

Pricing · WellOPS

Scoped to your operation.

You buy WellOPS by WorkSync; the tracks beside this are rollout scopes of that one purchase.

GOOD
Route Optimization + Field Data Capture
BETTER
adds DataHub + Work Engine + Field Work Management
BEST
adds Field Safety + Operations Dashboard

Impact Guarantee · license fees only when the metrics move

Scoped to your well count and systems with our implementation team when you plan your pilot. The pilot runs four weeks on one field, and DataHub is included.

See How Pricing Works

See Your Wells Ranked

Read the 40-page research white paper →

Before you ask

Common questions

What is the WellOPS Route Optimizer module?

Route Optimizer is the WellOPS module that turns the ranked work list into crew-specific daily plans: a constraint-based solver assigns and sequences stops across every crew, respecting qualifications, time windows, hours of service, yard locations, and equipment co-routing, then delivers the plan to the truck cab on mobile. It is the execution layer of pump by priority. The category-level buyer guide, including how oilfield routing differs from delivery routing, is at route planning software for oil and gas.

How does Route Optimizer replace a fixed pumper route?

A fixed route visits the same wells in the same order regardless of what changed overnight. Route Optimizer rebuilds the day from current conditions every morning: which wells deviated, what each issue is worth, who is qualified, and what fits in the shift. The route changes daily because the field changes daily; the deployment-measured result is 35% fewer miles for the same production coverage.

Do I need Work Engine for Route Optimization to work?

The GOOD tier (Route Optimization + Field Data Capture) can run on static priorities you provide. The BETTER tier adds Work Engine for dynamic economic ranking, which is where most of the 35% fewer miles driven (deployment figure) comes from. Without Work Engine, Route Optimizer optimizes distance; with it, the objective is cash flow per crew-day.

How is this different from generic fleet-routing or telematics tools?

Those tools optimize for distance or time. Route Optimizer optimizes for economic impact per crew-day, factoring production at risk, equipment urgency, safety constraints, and crew qualifications. We integrate with the fleet telematics you already run for the underlying vehicle data.

Does this work for mixed fleets (pumpers + technicians + contractors)?

Yes. Each crew type has its own qualifications and time windows. Contractor dispatch is handled with the same engine, qualifications flow from Vendor Management and ISNetworld integration.

What does it cost?

You buy WellOPS by WorkSync; Route Optimizer is its route optimization capability, and the tracks are rollout scopes of that one purchase. GOOD (Route Optimizer + Field Data Capture), BETTER (adds DataHub + Work Engine + Field Work Management), BEST (adds Field Safety + Operations Dashboard). Scoped to your well count and systems with our implementation team when you plan your pilot.

How fast can we deploy?

The stand-up is four weeks: telematics and HR integration in week one, the optimization engine configured in week two, crews trained and running on the mobile app in weeks three and four.

Is this validated in the field, or just a model?

Both. Our research white paper formalizes the problem (a multi-class vehicle routing problem with synchronization constraints) and was validated against a 12-month, 5,000-well, three-basin deployment: 35% fewer miles driven and 15% higher free cash flow on the same crew (deployment figures). The full 40-page paper, including the solver and the economic model, is linked above.

See Route Optimizer on your data.

Bring one area, your crew roster and your qualifications. We solve a real day against your own stops and show you the plan beside the route your crews actually drove, with the value difference between them.