WellOPS · Prioritization · Work Engine

The Work Engine is the most sophisticated prioritization engine in the oilfield.

See Your Wells RankedView a Sample 6 AM Plan
The WellOPS Command view on a laptop: the field map with every open flag ranked beside it
Demo screen, synthetic data
It takes OT data, financial data, and the rest of your operational record and stitches them together into closed-loop prioritization: every open job priced in dollars per day at risk, ranked against every other open job on one economic ruler, and delivered to the truck cab by 6 AM with the qualified crew and the solved route already attached.
The output: a ranked plan
Today’s plan · 06:00
5 Critical
#Well, reason, deferred, driveValue / day
01
Alderridge F-7H, CriticalHigh Fluid Level · 96 BOE · 8 mi
$3,939/d
02
Pellmarsh 1-5, CriticalESP Underload · 71 BOE · 17 mi
$3,336/d
03
Sabelgate Unit 7, CriticalCompressor Down · 63 BOE · 15 mi
$2,807/d
04
Bringate 1-4, CriticalGas Lock · 53 BOE · 9 mi
$2,711/d
05
Thanegate Unit 1, CriticalHigh Fluid Level · 47 BOE · 14 mi
$2,262/d
Top 5 of 46 flags shown · synthetic demo dataPlan total, 4 crews · 25 stops $34,214/d · 375 mi

What the Work Engine produces each morning: every open item priced and ranked on one ruler. Synthetic demo data, generated.

It is the APC of work management

It is the APC of work management: continuously balancing cash flow, safety, and the proactive against the reactive.

Running today at a top 25 private producer across 5,000+ wells in three basins. You buy WellOPS by WorkSync; the Work Engine is the prioritization capability inside it.

What it does

Seven capabilities that turn an unranked alarm queue into a priced, routed day.

Ingests OT, financial, and operational data on read-only connections
SCADA tags, historian trends, well tests and manual gauges on the OT side. Realized price by stream, working interest, lifting cost and cost history on the financial side. Equipment plans, regulatory clocks, crew qualifications and drive time for the constraints. Connections are read-only, stand up on credentials your team issues, and stay clear of your control network.
Scores every well against what it should be doing, not a fixed threshold
Each well carries a model of its own expected behavior this week, built from its decline, its lift type and its recent history. A flag is raised on departure from that model, so the engine keeps working as wells decline and nobody re-tunes limits by hand across thousands of wells.
Prices every flag in dollars per day at risk
Production at risk per day of inaction, valued at your realized price and your interests, discounted by how likely the intervention is to recover it and by what the intervention costs. A gassy well and an oil-weighted well with the same pressure drop come out an order of magnitude apart.
Ranks proactive, reactive, safety and regulatory work on one ruler
One queue, not four. Regulatory deadlines stay absolute where the regulator sets them; everything else earns its position by what it is worth today. The reason a job ranks where it ranks travels with the job.
Delivers the plan to the truck cab by 6 AM
Mobile and offline-first. Every crew opens their ranked list before leaving the yard, each line carrying what tripped, what it is worth, and what a good outcome looks like.
Re-ranks mid-shift, within limits
Re-ranking fires on a defined trigger set (a well down, a higher-value flag, a crew change, weather) and pushes only to affected crews, behind a minimum-improvement bar so small re-orderings are not worth the cognitive cost. In-progress work is interrupted only by a safety gate.
Learns from every close-out
Each completed job answers whether the flag was worth the visit. False positives, recovery outcomes, actual durations and every override with its reason code feed back into the scoring. Two operators can buy identical software; the one whose loop is closed accumulates calibration the other never gets.
Aerial view of a fenced gravel yard with white upright storage tanks, smaller stainless vessels, pipe racks and blue skid buildings, with brown winter fields beyond
Storage tanks and pipe racks from above · Photograph

What the office sees

One board, priced, with today’s route beside it.

The engine's output is not a report. It is the board the office works from: every open flag on the field in one order, and each crew's day drawn from the same ranking. The figure below is the synthetic field, in the product's own layout.
WellOPS
Synthetic field · Today, 06:00
On the line
$66,094/d
Open flags
46 of 148 wells
On a route today
25
Waiting for a better day
21
Ranked board51526
  1. Alderridge F-7HCriticalHigh Fluid Level#0127 · 30.9h open · rod pump$3,939/d96 BOE · #1 on route
  2. Pellmarsh 1-5CriticalESP Underload#0136 · 22.5h open · ESP$3,336/d71 BOE · #1 on route
  3. Sabelgate Unit 7CriticalCompressor Down#0138 · 3.5h open · gas lift$2,807/d63 BOE · #2 on route
Crew A, today7 stops · 2h 39m drive · $10,331/d
1234567A
The board and the route are drawn from the same synthetic field the rest of this site uses, in the product’s own shapes. Field units, not geography. Synthetic demo data, generated. No customer data, no real geography, no real operator.

What the score is made of

Four terms, one number, one queue.

The engine resolves every open item to a single figure: dollars at risk per day of inaction.
Exposure
What the well or facility is losing, or stands to lose, per day while the item sits: deferred production measured against what that well should be doing this week, plus the downstream consequence if it compounds into a shut-in or a workover.
Value
Exposure converted to dollars on your realized price by stream, your working interest and your net revenue interest, net of lifting cost. This is the term that makes a BOE stop being a BOE and separates an oil-weighted well from a gassy one.
Probability
How likely the intervention is to recover the exposure, learned from your own close-out history for that failure mode, that lift type and that crew type. It is what keeps a low-confidence long shot from outranking a certain fix.
Cost and constraint
What the visit consumes: crew hours, drive time, equipment that has to travel with it, and any qualification that limits who can do it. Regulatory and safety clocks enter here as hard bounds rather than as score, because a deadline is not negotiable against dollars.
Worked illustration · not a measured claim

That figure is what lets a plunger change, a compressor vibration trend, an LDAR survey and a tank approaching capacity sit in the same ranked list without anyone arguing about which queue owns them.

Two flags, same alarm class, two orders of magnitude apart.

Low-pressure flag, low-rate well

A few barrels a day of exposure, gas-weighted, high recovery probability whenever someone gets there, and a stop that adds an hour of driving. It ranks into the backfill and gets picked up when a crew is already nearby.

Same flag class, high-rate oil producer

Thousands of dollars a day of exposure at your realized oil price and your working interest, compounding while the well sits, and a qualified crew twenty minutes out. It goes to the top of the day.

A classical exception engine renders these two items identically: same color, same row height, same notification. The scoring is what separates them, and the routing is what acts on the separation.

The full mechanism guide: sensing, rules, delivery, and the five ceilings 

The work loop

Every item has a state, and every state has a reason.

A work item runs Generated to In-Progress to Complete, and two branches leave the middle. Nothing disappears from the record: an item that is escalated or deferred keeps its dollars, its reason code and its place in the ranking when it comes back.
ForwardReturn to the rankingPick a state

  4. Two branches leave In-Progress

  6. ↑ Complete, Escalated and Deferred all return to the ranking

Pick a state to see what happens there and where the item goes next.

The Work Engine state machine. Re-ranking fires on a defined trigger set and pushes only to affected crews; in-progress work is interrupted only by a safety gate.

Pricing · WellOPS

Scoped to your operation.

You buy WellOPS by WorkSync; the tracks beside this are rollout scopes of that one purchase.
GOOD
DataHub + Work Engine.
BETTER
Adds Opportunity Scoring + Route Optimization.
BEST
Adds Field Work Management, Field Data Capture, 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.

Reply within 1 business day · 4-week pilot · license fees only when the metrics move · GOOD / BETTER / BEST rollout scopes · for VP Operations and Field Superintendents

See Your Wells Ranked
See How Pricing Works

Proof

Same crew, 15% more free cash flow, 35% fewer miles driven.

  • 15%
    FCF uplift on the same crew, measured in live deployment
  • 35%
    Fewer miles driven, same production coverage, measured in live deployment
  • 5,000+
    Wells, measured in live deployments

Deployment figure from live operations · a top 25 private producer · Western Anadarko, Permian, Wyoming · 5,000+ wells

Read the full 3-basin case study 

Before you ask

Common questions

How is Work Engine different from a well-lifecycle tracking system?
Tracking systems record work that's already been identified. Work Engine GENERATES ranked work from SCADA anomalies, engineering recommendations, and production drift, then routes it to crews. Different jobs. They complement: your tracking system stays as system of record; Work Engine runs the operational loop on top.
Do I have to replace Enertia, Quorum, or Oildex?
No. Work Engine integrates with them read-only through DataHub. Operational data flows in; financial results flow back. Named systems stay as systems of record.
How fast can we deploy?
The stand-up is four weeks: a read-only connection in week one, configuration and the first ranked plan in week two, and the ranked plan in the field in weeks three and four, with pilot crews running on it in week three and crews live by week four. The first read of your metric against the signed baseline comes at week four.
What does Work Engine cost?
You buy WellOPS by WorkSync; Work Engine is its prioritization capability, and the tracks are rollout scopes of that one purchase. GOOD (DataHub + Work Engine), BETTER (adds Opportunity Scoring + Route Optimizer), BEST (adds Field Work Management, Field Data Capture, Operations Dashboard). Scoped to your well count and systems with our implementation team when you plan your pilot. See /pricing for how the model works.
What data does Work Engine need to work?
SCADA / historian data (pressures, flow rates, temperatures, runtime hours) and production accounting data form the foundation. Optional: CMMS work order history and engineering recommendations sharpen the ranking further. If you have Ignition + Enertia, you have enough.
Does this work for small operators?
Sweet spot is 500+ wells. Below that, superintendents can usually run priority from memory. Above 500 wells, the economic ranking compounds, more wells, more data, better rankings.

The category, end to end, is covered in the complete guide to pump by priority.

See Work Engine on your data.

Bring one field. We run the engine on your data and show you the ranked plan your crews would have worked, with the dollars attached. The 4-week pilot puts it in the truck cab, under the Impact Guarantee: we charge when your number moves.

See Your Wells RankedView a Sample 6 AM Plan