Upstream Optimization · Pillar

Upstream optimization, on the data you already have.

Most upstream operators have spent millions on SCADA, CMMS, ERP, and production accounting. They still build the morning plan in Excel. Upstream optimization is the discipline of turning that data into a cash-flow-ranked daily plan, without changing headcount or the systems your team already trusts.

Take the Blind Spot Test 

Definition

What is upstream optimization?

Upstream optimization is the general term for turning operational data (SCADA, ERP, CMMS, production accounting, GIS, weather) into a ranked daily work plan that moves cash flow per BOE.

It is not a new system. It is a new workflow that sits on top of the systems your team already runs.

The operating model that delivers it has a name: pump by priority. Economic scoring on every exception, value-dense routing, and closed-loop learning; the complete guide, the definitions, and the math live on that page.

Largest reference deployment · 5,000+ wells · 3 basins · part of our 10+ operator customer base

  • 15%
    free cash flow uplift on the same wells, same crew
    Deployment figure
  • 35%
    fewer miles driven at equal economic coverage
    Deployment figure
  • 5,000+
    wells under live deployment across three basins
    Deployment figure

The most sophisticated prioritization engine

The five levers of upstream optimization.

Each lever maps to a WorkSync module. Fit-for-purpose. Plug-and-play. Buyers can pilot any single lever for 4 weeks under the Impact Guarantee.

Lever 01

Cash-flow-weighted task ranking

Every potential field task (gauge run, anomaly investigation, PM, leak repair) gets scored by its dollar-impact on the day. The top 220 stops across 10 crews surface as the ranked work plan. Result: the highest-value work gets done first, not the loudest alarm.

→ Work Engine

The sun rising directly behind a working pumping unit, a lease road in the foreground and a second unit and power poles on the horizon
A pumping unit and its lease road at sunrise · Photograph · Photo: James Gabbert, CC BY-SA 4.0

The 4-week pilot

The stand-up is a product, not a project.

One week to integrate, two weeks to configure, crews on the ranked plan by week four, under the Impact Guarantee: we charge when your number moves.

The full playbook (sprint structure, acceptance gates, and what your team actually has to do) is documented on the productized rollout page.

More detail

Upstream operations software for the mid-tier, where the spreadsheet broke and the super-major stack is overkill.

The 500–5,000 Well Window

Below 500 wells the superintendent runs from memory. Above 10,000 wells the super-major stack is the answer.

The middle, where most US private and mid-cap operators live, has an unmistakable pattern: SCADA, ERP, CMMS, and accounting are already invested in, but the production operations software layer that turns those investments into ranked daily action is missing.

These are the buyers WorkSync is built for: PE-backed PDP roll-ups where LOE is the whole game, and lean independents with no internal software team and no appetite for an 18-month build.

The supermajors built this internally a decade ago; the mid-tier has been 10-plus years behind with no productized path. Six pain points repeat across this window. Here is each, and the WorkSync module that addresses it.

See 22 production-ops use cases

4-week pilot on one field · 30-day deploy · sits on top of your existing stack

Where you sit on the well-count axis determines which software actually fits.

The well-count map

Vendors push their production operations software as universal. It isn’t. Simple pumper apps fit independents. Supermajor platform suites fit super-majors. The 500–5,000 well window is its own category.

Below 500 wells

Independent operator

Superintendent can hold the asset base in their head. One foreman, 3-6 pumpers, paper or a simple pumper app for capture, standalone production accounting. No SCADA or limited.

Software they need: A simple pumper app for field data capture + standalone production accounting

WorkSync fit: Spreadsheets still work. The 6 AM ranked plan needs SCADA + production accounting + a critical mass of wells to compound.

500–5,000 wells

Mid-tier upstream: the sweet spot

Multi-pad operations across one or two basins. SCADA and historians in place. Production accounting in an established system of record. A legacy CMMS, or shadow IT filling the gap. Procurement runs through the operating org rather than a standing committee.

CFO publicly defending FCF and LOE/BOE.

Software they need: Ranked work execution layer that sits ON TOP of the existing stack. Turns SCADA + accounting + CMMS data into a daily plan delivered to the truck cab.

WorkSync fit: · this is the WorkSync sweet spot ·

5,000–10,000 wells

Large independent / public mid-cap

Multi-basin. Multiple SCADA vendors. M&A history. Enterprise ERP and EAM platforms. Procurement with committee signoff. Public earnings calls referencing capital efficiency.

Software they need: Same as 500-5,000 + asset integration story (M&A integration, multiple SCADA reconciliation). WorkSync still fits but procurement cycle lengthens.

WorkSync fit: Fits. The engagement is scoped to your well count and systems with our implementation team, and the first one is still four weeks on one field at this scale. Common pattern: land in one division, expand company-wide.

10,000+ wells

Super-major / large public

Global operations, multi-decade enterprise software stack, dedicated digital transformation budget. Supermajor platform suites and enterprise CMMS at scale. Multi-year procurement.

Software they need: Enterprise digital twin + reservoir / process modeling suites. Internal data science teams build custom applications.

WorkSync fit: WorkSync sits as ONE component of a larger stack at this scale. Possible but not the typical buyer.

The same set of problems show up at every mid-tier operator we work with.

Six pain points that repeat across the window

Each pain has a specific WorkSync module that addresses it. Solve them in any order; the architecture is modular. Most operators land on whichever pain is loudest this quarter, then expand from there.

The spreadsheet broke

Worked at 200 wells. Doesn't at 1,500. Superintendent can't hold the asset base in their head; the morning phone tree takes 90 minutes; pumpers run yesterday's priorities because nobody updated the route.

Addressed by: Work Engine + Route Optimization (ranked plan delivered to truck cab by 6 AM)

SCADA alarms became noise

200+ daily alarms with no economic ranking. Pumpers numb out and miss the real ones. False-alarm fatigue erodes the gains your SCADA investment was supposed to deliver.

Addressed by: Anomaly Detection + Pump by Exception + Reinforcement Learning

Engineering hours go to data entry

Hydraulic models are quarterly artifacts that are wrong by the time you need them.

Addressed by: FlowSync: auto-build hydraulic models in minutes; native exports for HYSYS, OLGA, PIPESIM, EPANET, 15+ simulators

CFO is asking for LOE/BOE you can't produce

"Show me cohort returns." "Show me LOE/BOE by basin." "Defend the rig count." The IR slide is built three weeks after close in a separate spreadsheet by a separate team. Field reality and IR narrative drift apart.

Addressed by: Operations Dashboard + Economic Scoring (live LOE/BOE from the same data Field Ops dispatches on)

Acquisition closed; two ops stacks now run in parallel

18+ months of dual-stack operations. Synergy slips to the right. Acquired-asset LOE/BOE diverges from legacy fleet. Board wants the synergy capture report at 90 days; you have a slide projection.

Addressed by: Rapid Integration + DataHub: Day 91 produces one ranked work plan across the merged fleet

TRIR pressure from banks and insurers

Safety performance is now a financing input, not just an HSE number. Lone-worker hardware ends at the device. Qualification gating, JSA automation, contractor competency are still manual.

Addressed by: Field Safety: situational awareness + dispatch-time qualification enforcement

Proof

The mid-tier breaking point: cross 1,500 wells, often overnight via M&A, and the spreadsheet stops working. WorkSync puts the ranked plan in the truck cab in four weeks, on the same crew and the same SCADA. Measured across live deployments: 15% more free cash flow.

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

Read the full 3-basin case study →

Pick the loudest pain. Land there. Expand from there.

Built for the 500–5,000 well window

Four weeks to stand up under the Impact Guarantee, license fees only when the metrics move. Then you run it for three-plus months and let the number prove itself. No rip-and-replace.

Production operations software that sits on top of the SCADA, ERP, CMMS, and GIS systems you already own.

Reply within 1 business day · 4-week pilot · license fees only when the metrics move

Increase production with the crew you already have.

For Production and Operations leadership

Wells go down every day, and every down well, underperforming lift job, and haul competes for the same field hours. On most operations that competition is settled by habit and geography.

Settle it by dollars instead and base production rises on the same payroll, because the highest-value work gets done first. WellOPS runs that math every morning.

15% FCF uplift on the same crew, measured across 5,000+ wells in live deployments. Live in 4 weeks.

Grow production without growing headcount is the ask. The scheduling math is the obstacle.

The problem

New wells land on the same field organization every week, base decline never pauses, and efficiency gains get declared permanent, so the crew stays the size it is. That leaves one lever: which well a field team member drives to first.

Sequencing hundreds of open jobs against production at risk, crew qualifications, drive time, and safety constraints is scheduling math no person can run in their head at 5:40 AM, so it gets run by memory and proximity instead.

The queue that should decide cannot tell a nuisance from a production loss.

A 5 BOPD stripper alarms with the same color and sound as a 200 BOPD producer, and past roughly a dozen items an exception list stops being a work list and becomes background noise.

A deferred barrel is free cash flow already committed to shareholders.

The consequence

When the highest-value well waits behind routine stops, its deferment compounds by the hour, and the loss never appears on a report as a decision anyone made.

Recovered deferred production is worth a 2 to 5% production uplift on a typical operation (modeled, aligned to the published Alvarez and Marsal worked example), and the scarce resource that recovers it is a qualified field hour landing at the right well before the problem compounds.

The same misallocation hides in the downtime report. With gas realizing pennies and oil realizing dollars, an hour down is not the same hour everywhere, yet downtime rolls up in BOE.

A field plan that cannot see revenue at risk spends crews on the wrong wells and reports the average.

The computer runs the scheduling math. Your people run the field.

The WorkSync decision

WellOPS prices base production work in dollars per day: every down well, every workover candidate, every lift job and route stop, ranked against everything else open in the field.

The ranked plan is in the cab by 6 AM with the reason each well is on it, and close-out at the wellhead feeds the outcome back into the ranking. Flag, Price, Rank, Route, Execute, Learn: production capacity from the organization you already have.

The production day, ranked by revenue at risk instead of visit cadence. The wait-and-see judgment on the stripper stays yours; the system ranks within your rules. Illustrative data.
P1Well 233H: down 14 hours, gas-lift restart$5.1k/d
P1Battery 14: ESP drawing down, deferment risk$8.4k/d
P2Well 118: rod pump trending off, workover candidate$2.2k/d
P3Well 87: low-rate stripper, wait-and-see holds$0.2k/d

Exception-based surveillance already makes the capacity case: Alvarez and Marsal’s 2015 model of the two operating models puts lease operator value-added time at about 25% of the day under fixed routes and about 60% under exception-driven operations (illustrative model, not a measured study).

Pump by priority takes the remaining step, deciding which of those value-added hours land first, and a well turned over today enters the ranking and the routes today: no spreadsheet rebuilt, no route redesigned, no new hire to keep track of it.

The number that moved was cash flow, on the same crew.

Proof

  • +15% free cash flow uplift on the same crew, measured across 5,000+ wells in live deployments
  • 2 to 5% production uplift from recovered deferred production (modeled, aligned to the published Alvarez and Marsal worked example)
  • 4 weeks to field deployment, standard WellOPS rollout

Deployment figures from live operations at a top 25 private producer. The 4-week pilot is how you find out what transfers, against a baseline you set.

Go deeper

Deferred production, priced

The mechanism behind the 2 to 5% band: how deferment accumulates, and how a ranked queue recovers it.

Read the deferred production page →

Surveillance that ends in a truck

Production surveillance as WellOPS runs it: detection wired straight into a priced, ranked, routed field day.

See production surveillance →

The engine that ranks the day

The Work Engine builds the ranked plan: inputs, scoring, constraints, and the closed loop that keeps it learning.

Walk the Work Engine →

Don’t leave production on the table.

Bring us one field’s data. We’ll show you what your crew would have worked on this morning, and what it was worth.

View a Sample 6 AM Plan, no form →

Frequently asked

What VPs of Ops ask before they commit.

What is upstream optimization?

The general term for turning the operational data you already collect (SCADA, ERP, CMMS, production accounting) into a cash-flow-ranked daily plan that moves the metric a CFO cares about, without changing headcount.

The operating model that actually delivers it at field level has a name: pump by priority.

How is upstream optimization different from production optimization?

Production optimization narrowly targets per-well output: rod-pump speed, choke settings, gas-lift rates.

Upstream optimization is the broader discipline of optimizing field economics: which wells get visited today, what work is highest cash-flow impact, which crew is the right qualification fit, and how the route should be sequenced.

What is the cash-flow impact?

Across our customer base (10+ operators, 5,000+ wells in three basins) the largest deployment achieved 15% free cash flow uplift on the same crew and 35% fewer miles driven at equal economic coverage (deployment figures).

What data do I need to start?

Whatever you have. WorkSync uses physics-based statistical models that work against the data sources you already run. SCADA is helpful but not required.

Does it replace our SCADA / CMMS / ERP?

No. WorkSync sits on top via the DataHub. Your systems of record stay; we add the intelligence layer.

How does this relate to pump by exception and pump by priority?

Pump by exception is the starting point: visit only deviating wells. Pump by priority is the destination: economic ranking, value-dense routing, and closed-loop learning on top of the exception discipline.

When operators search for upstream optimization, pump by priority is the operating model they are looking for; the complete guide lives on our pump by priority page.

How fast can it be deployed?

Under a week to integrate. Two weeks to stand up. Four weeks for crews on the ranked plan. The 4-week pilot runs on the stack you already own, under the Impact Guarantee: license fees only when the metrics move.

The productized rollout page documents the stand-up sprint by sprint.

What is the Impact Guarantee?

Pick the operating metric that matters. We run the module for 4 weeks. License fees only when the metrics move: if the number you anchored on moves, we keep going. If it does not, you walk away, no kill fee.

What well-count window is "mid-tier" upstream?

For software-fit purposes, 500 to 5,000 producing wells. Below 500 wells, superintendents can run the asset base from memory and a simple pumper app plus standalone production accounting cover the gap. Above 10,000 wells, supermajor platform suites start to fit.

The 500 to 5,000 window has its own pattern: SCADA + ERP + CMMS + accounting already invested in, but the intelligence layer that turns those into ranked daily action is missing.

Why is mid-tier the "sweet spot" for ranked work execution?

Three reasons. First, SCADA and accounting investments already exist, so there is enough data for the closed-loop architecture to compound.

Second, the operating leader is still close enough to the field that a four-week pilot on one field is a real experiment rather than a program; mid-tier does not run 18-month enterprise transformations. Third, the LOE/BOE pressure is most acute here.

Large independents and mid-cap public operators are publicly defending capital efficiency on every earnings call.

What software does WorkSync replace at this scale?

Generally none. WorkSync sits on top of the systems already in place: your SCADA and historians, production accounting, CMMS, and GIS. The architecture is read-from-existing, not migrate-to-new.

Some mid-tier operators do choose to retire shadow IT (legacy CMMS, custom field-data apps) over time as WorkSync's coverage expands, but that's a Phase 2 decision, not a deployment requirement.

How does pricing work at mid-tier scale?

Land with DataHub read-only or start with a single FlowSync model engagement, then expand as the platform proves out.

Scope is set to your well count and systems with our implementation team when you plan your pilot, and the first engagement is four weeks on one field. Under the Impact Guarantee, license fees only when the metrics move.

How long does deployment take for a mid-tier operator?

Integration is under 1 week. Standup is 2 weeks (full SCADA + ERP + CMMS + GIS connection). Field rollout is 4 weeks. Most mid-tier operators are live with ranked plans in the truck cab within a quarter from kickoff.

What if we just acquired another operator and want to integrate?

See /m-a-integration-oil-gas-software for the 90-day asset-integration playbook. Common pattern at mid-tier scale: M&A pushed the operator past 500 wells, the spreadsheet broke, integration becomes the trigger for ranked work execution adoption. Day 91 produces one ranked work plan across the merged fleet.

Are your best people working on your most valuable work today?

Don't leave production on the table.

Four weeks on the stack you already own. Move the metric you anchored on: license fees only when the metrics move.