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 how a contract pumper route slots in as the response layer.
The honest position here: full industrial SCADA is the right system for high-volume horizontals and pipelines. For independent operators running stripper wells, a lighter system paired with a contract pumper route is usually the right pick. TinyPumper is the response-layer tool built for that second case.
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 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 contract pumper flags an issue back to the operator.
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.
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 Paired with a Contract Pumper Is the Right Pick
Three profiles where the light-monitoring-plus-pumper-route model is the right fit.
- Stripper wells with remote exposure. Low-volume wells that do not justify full SCADA but where visibility between pumper visits catches theft, leaks, and equipment failures.
- Multi-operator contract pumper routes. The contract pumper works for multiple operators. A unified monitoring feed lets the pumper prioritize stops.
- Operators wanting incremental coverage. Monitor the tanks and wells where the economics pay off. Skip the rest.
TinyPumper is the response-layer tool for case two and case three. It coordinates the pumper route across multiple operators’ assets and pulls in monitoring signals so the pumper decides which stops need attention today.
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 | Small-to-mid independents |
| Contract pumper coordination with monitoring | TinyPumper | Contract pumpers, producing companies using contract pumpers |
| 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.
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.
Who This Page Is Not For
This page is not for operators running full industrial SCADA with dedicated controls staff. 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 operators and contract pumpers evaluating a light-to-mid monitoring system paired with a pumper route workflow.
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. Response-layer tools like TinyPumper for contract pumper coordination add a per-user subscription on top.
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. For most stripper wells, read-only light monitoring is the right scope.
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 Plus Pumper Route Works?
If you are a contract pumper or a producing company using contract pumpers, TinyPumper is the response layer that turns monitoring signals into a prioritized route.
See a route, a pumper day, and how the data flows back to whoever pays the pumper. No sign-up to look.
P.S. TinyPumper is the wrong tool for operators running full industrial SCADA across high-volume horizontal assets. Emerson, Honeywell, or AVEVA fit that tier. If you are running a contract-pumper route (or hiring one), TinyPumper is built for that job.