Picture the monitoring system with three of four layers. Sensors installed. Cellular humming. Dashboard live. No owner. The H2S alarm trips at 2:14 am on a Tuesday, the email sits in a shared inbox nobody monitors overnight, and by the time anyone looks at the alert the crew on the lease has already figured it out the hard way. The producer paid for the hardware, the comms, and the software. The fourth layer (response) was never scoped. The system was cheaper to buy than it was useful in production.
An oilfield monitoring system is the whole stack that turns a remote well, tank, or compressor into something you can see from a phone or desk. Hardware in the field, communications, software on the back end, and the response workflow that decides what anyone does with the data. Most buyers shop the pieces separately and end up with a system that has three of the four. This page walks through how the pieces fit, what each layer costs, and where TinyPumper fits as the SCADA alternative for continuous oilfield monitoring on conventional sites.
The honest position here: full industrial SCADA is the right system for high-volume horizontals, compression, injection, and pipeline work where actuation and supervisory control genuinely earn their keep. For the conventional sites where SCADA either never penciled or is now breaking down and costing more to maintain than it returns, a lighter system paired with a phone-first field workflow is the right pick. TinyPumper is built for that second case, and it works whether the producer runs 50 wells or 5,000.
The Four Layers of an Oilfield Monitoring System
Every real monitoring system has four layers. Skipping one guarantees the system is cheaper to buy and useless in production.
1. Field hardware (sensors and RTUs)
Physical devices at the well or tank that read a signal and encode it.
- Tank level sensors. Ultrasonic, radar, or float-based. Report current level and rate of change.
- Pressure transducers. Tubing pressure, casing pressure, line pressure.
- Motor and pump monitors. Runtime, strokes per minute, motor current, pump-off detection.
- Compressor monitors. Runtime, trip alarms, gas throughput.
- Gas and H2S detectors. Safety-critical alarms.
- RTUs (remote terminal units). Integrate multiple signals from one wellsite, send them upstream.
Hardware cost ranges from a few hundred dollars per tank for a basic cellular level sensor to several thousand per site for a multi-channel RTU.
2. Communications
How the signal gets from the field to the back end.
- Cellular. Most common. Simple, reliable where signal is available, monthly data plan per device.
- Satellite. Remote leases without cellular coverage.
- LoRa and private RF. Campus-scale networks for dense well clusters.
- Wired. Legacy pipeline and facility installations.
For most independent operations, cellular covers the job. Satellite only when cellular truly is not available.
3. Software (dashboards, alerts, history)
The layer that makes the data useful.
- Live dashboards. Current reading per well, per tank, per asset.
- Historical trends. Hours, days, weeks of history to spot anomalies.
- Alerts. Threshold-based (tank level, pressure, runtime) and anomaly-based.
- Reports. Daily, weekly, monthly rollups for operations and regulatory use.
- Integration. API or file feed into production accounting, pumper apps, or broader operations software.
This is where most operators overbuild. A dashboard no one watches is just a line item on the credit card. Software value is measured in response, not features.
4. Response workflow
The layer everyone forgets. Who acts on the data.
- The pumper route. If the data flags a tank is filling faster than expected, the pumper (company or contract) visits that lease first today.
- Operations staff. Who watches the dashboard during business hours.
- Alerts and on-call. Who gets paged at 2 AM when an H2S alarm trips.
- Escalation. How a field flag reaches the ops lead or owner fast enough to act on.
Monitoring without response is decoration. A system that flags a tank theft overnight and no one checks for three days is worse than no monitoring at all, because it creates the illusion of coverage. The whole point of remote monitoring across the lease is that the signal reaches someone who can act on it.
How the Pieces Cost Out
A reasonable 10-site light monitoring system (tank levels, basic runtime, cellular, software) costs roughly:
| Layer | Typical cost |
|---|---|
| Hardware (10 sites) | $8,000 to $25,000 one-time |
| Installation | $2,000 to $8,000 one-time |
| Cellular data plans | $50 to $150 per site per month |
| Software subscription | $50 to $300 per site per month, tiered |
| Response workflow (pumper time) | Varies by operation |
For 10 sites, total first year runs $15,000 to $50,000 depending on tier. Break-even is a single averted theft or one avoided overnight blowout.
When a Full Industrial SCADA System Is the Right Pick
Four profiles justify full SCADA.
- High-volume horizontal assets. Single-well production rates high enough that downtime is thousands of dollars per hour.
- Pipeline and midstream operations. Custody transfer, compression, pressure management.
- Regulatory-driven monitoring. Air emissions, continuous flow measurement on regulated wells.
- Dedicated controls staff. In-house instrumentation technicians and a controls engineer.
If none of those fit, full SCADA is overbuilt.
When a Light Monitoring System Is the Right Pick
Three profiles where a light monitoring system paired with a phone-first field workflow fits better than full SCADA.
- Conventional wells and tank batteries where SCADA never penciled. Low-volume sites that could not justify the capex, the wiring, and the ongoing maintenance. Visibility between pumper visits catches theft, leaks, and equipment failures without the six-figure install.
- Aging SCADA that is breaking down. The sensors drift, the hosts need babysitting, the maintenance contracts cost more than the sites return. TinyPumper is the drop-in replacement that kills the maintenance drag.
- Incremental coverage inside a larger operation. A producer running 1,500 wells can have SCADA where it earns its keep and TinyPumper on the long tail of conventional sites where it never did. Same producer, mixed stack, site-by-site economics.
TinyPumper is the tool for all three cases. Producers buy it whether they run 50 wells or 5,000. The decision is never well count. It is whether the site is one where SCADA either failed the math or failed under maintenance.
Monitoring System Vendors by Fit
| System profile | Typical vendors | Best fit |
|---|---|---|
| Full industrial SCADA | Emerson DeltaV, Honeywell Experion, AVEVA System Platform | Majors, midstream, high-volume upstream |
| Mid-tier asset monitoring | Detechtion Technologies, Emerson Roxar, Sensia | Mid-size independents |
| Light monitoring (tank-level, cellular) | Digi, Senix, Ranger, TankLogix | Independents with scattered monitoring needs |
| SCADA alternative for conventional sites (hardware + app, flat-rate) | TinyPumper | Producers at any scale with conventional sites where SCADA does not pencil |
| Do-it-yourself | Open-source stacks (Node-RED, Grafana, InfluxDB) on cellular hardware | Technical operators with time |
The matchup between the system profile and operational scale is the decision. The wrong system for the operation is expensive even when the system is cheap.
Amateur vs Pro: How Producers Spec a Monitoring System
| The amateur… | The pro… |
|---|---|
| Buys the hardware first and worries about software later | Scopes all four layers (hardware, comms, software, response) before any PO |
| Picks a system on feature count | Picks a system on response time to an event that actually matters |
| Lets the system cover every site evenly | Covers the leases where drive time and event exposure justify the capex |
| Treats the field team as the last-mile afterthought | Designs the alert path backward from the pumper’s phone |
| Forces a full SCADA rollout onto conventional sites | Runs SCADA where it pencils and a flat-rate per-site layer on the rest |
The pros don’t buy bigger systems. They buy complete ones. Four layers, one owner per alert, the SCADA Silo closed before it forms.
Where the System Most Often Breaks
Three failure modes we see.
Hardware installed, software never connected properly. The sensors report but no one set up the dashboard or alerts. System delivers nothing. Fix: commit to a software rollout, not just a hardware rollout.
Dashboard with no owner. Software and hardware both live, nobody is assigned to watch the dashboard or act on alerts. Fix: name an owner (pumper, operations, on-call engineer). Monitoring without owner equals decoration.
Monitoring coverage that mismatches the route. The system monitors tanks on leases that do not need monitoring and leaves out leases where coverage would pay. Fix: match monitoring coverage to where pumper drive time is longest and theft or event exposure is highest.
What To Avoid When You Scope a Monitoring System
- Don’t skip the response layer. Monitoring without response is decoration. The Paper Lag shows up here in the new form: the alert fires, nobody owns it, the event gets found two weeks later anyway.
- Don’t let each vendor ship its own dashboard. The SCADA Silo multiplies logins. Pick the consolidation layer before vendor number two is added.
- Don’t over-cover the quiet leases. Coverage belongs where drive time is longest and exposure is highest. Even coverage is how budget gets wasted on the leases that did not need it.
- Don’t force full SCADA onto conventional sites. Where the math never penciled, a flat-rate per-site layer delivers roughly 99% of the upside without the wiring or the IT drag. That holds at any scale (50 wells or 5,000).
- Don’t fund hardware without funding the owner. A dashboard without a name on it is a subscription with no customer.
Who This Page Is Not For
This page is not for producers who genuinely need full industrial SCADA supervisory control and have the controls staff to run it. Emerson, Honeywell, AVEVA, and ABB are the honest picks for that segment. It is not for refineries, pipelines, or midstream operators. It is not for majors scoping enterprise upstream monitoring.
This page is for independent producers (anywhere from a couple dozen wells to 2,000+) evaluating a light-to-mid monitoring system on the conventional sites where SCADA either never penciled or is no longer worth the maintenance.
Related Pages
- Pillar: oilfield monitoring.
- Different phrasing: oilfield monitoring software.
- Mobile-first variant: oilfield monitoring app.
- Cross-cluster: oil and gas production software.
Frequently Asked Questions
What is an oilfield monitoring system?
An oilfield monitoring system is the combination of field sensors, communications, software, and response workflow that gives an operator visibility into wells, tanks, and facilities between physical visits. A complete system has all four layers. Most operators who buy a monitoring system that feels broken are missing one of the layers, usually response workflow.
What does a monitoring system cost for an independent operator?
A 10-site light monitoring system typically runs $15,000 to $50,000 in the first year, including hardware, installation, cellular service, and software. Full industrial SCADA at a 10-site operation would run several times that. TinyPumper, for comparison, is a flat rate per site (hardware one-time, monthly polling fee, unlimited sensors at the location, cellular included) so producers can model the cost site by site rather than pay integrator hours.
What is the difference between SCADA and a light monitoring system?
SCADA (supervisory control and data acquisition) adds actuation. A full SCADA system can start and stop pumps, open and close valves, and change setpoints remotely. A light monitoring system is read-only. It tells you what is happening. The pumper or the operations team decides what to do. On conventional wells where SCADA either never penciled or is no longer worth the maintenance, read-only monitoring plus a phone-first field workflow gets you roughly 99% of the upside without the capex or the IT drag.
Do I need a monitoring system if I have a pumper visiting daily?
It depends on drive time and exposure. If your pumper drives two hours each way and gauges a single tank, monitoring that tank pays off fast. If your pumper walks the lease every few hours, monitoring is usually not worth the cost. The decision is a math question about how much time the system saves and how much event exposure it covers.
Ready to See How a Light Monitoring System Works on Conventional Sites?
If you are a producer with conventional wells, tank batteries, or facilities where SCADA either never penciled or is breaking down, TinyPumper is the drop-in. Ten minutes of install, flat rate per site, no wires, no IT. Whether your field work is done by company pumpers or a contract pumping outfit, TinyPumper is on the lease because the producer bought it.
See the hardware, a pumper day, and how the data flows back to whoever owns the well. No sign-up to look.
P.S. TinyPumper is the wrong tool where you genuinely need full industrial SCADA supervisory control (high-volume horizontals, compression, pipeline work). Emerson, Honeywell, or AVEVA fit that tier. Everywhere else, the math favors TinyPumper, whether you run 50 wells or 5,000.