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

1. 01

   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.
2. 02

   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.
3. 03

   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.
4. 04

   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.
5. 05

   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.
6. 06

   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.
7. 07

   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.

1. 1 · Ingest

   Your existing data, validated before it is scored

   DataHub, included with the platform, pulls SCADA, production accounting, equipment history and asset lifecycle data into one well master. Sensor drift, stuck values and out-of-range readings are caught and quarantined first, because scoring an unrationalized queue produces precise rankings of garbage.
2. 2 · Rank

   Every job priced in dollars per day, then sorted on one ruler

   The engine assigns an economic-impact score to every open item: production at risk per day of inaction at your price deck and your interests, adjusted for recovery probability and intervention cost. Preventative maintenance, reactive anomalies, liquid management, safety and regulatory work all compete on that one number.
3. 3 · Execute and close

   Ranked plan in the truck cab by 6 AM, outcome back by close-out

   The Route Optimizer solves the ranked list into crew-specific days under qualification, hours and equipment constraints. Mobile, offline-first. The close-out generates the ticket and the accrual, and the outcome feeds the next ranking.

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