Manage by Exception · Operating Model
Alarm only on what matters. Rank by what pays.
Manage by exception is the operating model behind every efficient upstream operation: limited human attention goes only where the data says it pays. The discipline traces from Drucker through manufacturing and IT ops into oilfield SCADA. This page covers what the model actually requires, where it fails in practice, and how WorkSync closes the loop with economic ranking and reinforcement learning.
Definition
What is manage by exception?
Manage by exception is an operating model where leaders and field crews focus attention only on items that have deviated meaningfully from expected performance. Routine, in-spec activity is trusted to continue on its own. The limited human attention available goes to the small set that has moved out of bounds.
The inversion matters. Manage-by-walk-around scales linearly with headcount: if you double your wells you double your pumpers. Manage-by-exception scales with software: an exception-based system that continuously monitors 5,000 wells is the same shape as one that monitors 500 — only the input data set grows.
In upstream oil and gas this manifests as two specific applications: pump by exception (alarm and visit only deviating wells) and pump by priority (rank the deviations by economic impact). Together they replace fixed Monday-Wednesday-Friday route loops with a daily plan that only visits wells where attention is worth the windshield time.
The lineage
From Drucker to the oilfield.
Exception-based management is older than the SCADA that runs your wells. Knowing the lineage matters because it tells you what the discipline already knows about its own failure modes.
Peter Drucker formalizes manage-by-exception in "The Practice of Management" as a leadership doctrine.
Toyota Production System and statistical process control embed exception-based management into manufacturing lines.
IT operations adopt exception-based alarm management (Nagios, Tivoli, OpenView).
SCADA-driven exception alarms enter upstream oil and gas. The "pump by exception" workflow is born.
Economic scoring + ML anomaly detection layer ranking onto pump-by-exception. The next era.
Reinforcement learning + agentic field ops complete the closed-loop discipline.
The failure modes
Where exception-based management goes wrong, and how WorkSync fixes it.
Failure mode 01
Alarm fatigue
The failure
Most SCADA-driven exception systems generate hundreds of alarms a shift. Without ranking, crews triage by recency or loudness; the highest-value alarm gets buried.
The WorkSync fix
Continuous economic scoring: every flagged exception carries a dollar-impact estimate and a tier (P1 / P2 / HIGH / MED). The morning ranked plan is sorted by $, not by timestamp.
Failure mode 02
Stale "normal"
The failure
Wells decline. Equipment ages. Operating bands shift. Fixed alarm thresholds, set during commissioning and never updated, produce false negatives (real issues hidden behind a thresholds that has crept out from under the actual performance) and false positives (alarms that mean nothing).
The WorkSync fix
Continuously updated Arps decline forecasts per well, confidence bands per signal, and ML anomaly detection that learns each asset's normal individually rather than against a fleet-wide rule.
Failure mode 03
Missing economic ranking
The failure
Exception management without economic ranking is just an alarm list. Two wells deviating at the same time may have $12,500/day vs $90/day of revenue at risk. The 10x spread is invisible without scoring.
The WorkSync fix
Cash-flow-weighted task ranking. Every potential field task scored by dollar-impact. The top 220 stops across 10 crews surface as the daily ranked plan.
Failure mode 04
No closed-loop learning
The failure
Exception lists that don't learn from outcomes get progressively worse. When a flagged exception doesn't pan out, the next similar pattern keeps getting flagged at the same priority.
The WorkSync fix
Reinforcement learning closes the loop. Every completed task feeds outcomes back into the scoring models. Each week the plan ranks the right work more accurately.
Continue the cluster
Exception management is one piece of the upstream optimization discipline.
Companion pillars
The cluster
- Upstream Optimization→
The umbrella discipline
- Pump by Exception→
The definitive guide
- Pump by Priority→
Tasks ranked by $ impact
- Four Eras of Field Ops→
Where exception fits in the bigger arc
- 90-day Path Era 2 → 4→
How to upgrade your operating model
- LOE Reduction pillar→
Where exception management pays the bill
How the loop closes
Capability deep-dives
Modules that run it
Where to start
Frequently asked
What VPs of Ops ask about exception-based management.
What is manage by exception?
An operating model where leaders and field crews focus attention only on items that deviate meaningfully from expected performance. Routine in-spec activity runs on its own; human attention goes to the small set that has moved out of bounds.
How does it differ from manage by walk-around?
Walk-around is reactive and serial: check everything on a fixed cadence. Exception management inverts the loop: continuously monitor every asset, surface only deviations, visit where attention is provably worth it.
How does this apply to upstream oil and gas?
Two applications dominate: pump-by-exception (visit only deviating wells) and pump-by-priority (rank the deviations by economic impact). Together they replace fixed Monday-Wednesday-Friday loops with a daily plan that only visits wells where attention pays.
What does it require operationally?
A definition of "normal" per asset, a scoring layer that ranks deviations by dollar impact, and a delivery layer that gets the ranked plan into the field crew's hands before the shift starts.
What are the failure modes?
Alarm fatigue (too many exceptions, no ranking), stale "normal" (baselines that don't update as wells decline), and missing economic ranking (exceptions worked in arrival order, not in the order they pay).
See exception-based ranking on your data.
4-week pilot at no license cost. Move the metric you anchored on, or you owe nothing.