A cellular tank level sensor sits bolted to the top of a stock tank on a conventional lease in the Mid-Con. The battery has held for three years. The sensor is still broadcasting every fifteen minutes. The last time anyone logged into the vendor portal was the summer the engineer who installed it took a job at another company. The sensor is perfectly functional. The IoT program is dead. That is the most common failure mode in oil and gas IoT, and it has nothing to do with the hardware.

TL;DR. IoT in oil and gas is the network of connected devices (sensors, meters, controllers, cameras, trackers) that collect data from physical equipment and route it somewhere for action. For the full oilfield IoT framework (device categories, telemetry choices, and where a SCADA alternative fits), start with the pillar. The hardware works. The pilots die because nobody owns the data stream once the project engineer moves on. For an independent producer, the useful version usually boils down to pump-off controllers, high-level shut-ins, a gateway with radar and pressure sensors at the tank battery on conventional wells, and a pumper app that ties every gauge, run ticket, and downtime event into one record.

What IoT is not: a magic productivity boost or a substitute for a pumper walking the lease. It is a layer of connected sensors, and how much value you get depends on whether the data makes it to a decision you wouldn’t have made otherwise.

What IoT Devices Look Like in the Field

Upstream IoT devices that are actually deployed at scale:

  • Tank level sensors: ultrasonic or radar sensors that measure tank level continuously and send the reading over cellular, LoRaWAN, or satellite. Vendors include SignalFire, FreeWave, Sutron, and a dozen others.
  • Wellhead pressure transmitters: measure casing and tubing pressure with telemetry back to a cloud dashboard or SCADA server.
  • Flow meters: Coriolis, turbine, or positive-displacement meters at the lease sales point or at individual wells.
  • Rod pump monitors: dynamometer-based sensors that measure rod load and detect pump-off conditions, increasingly sold as IoT devices with cloud dashboards.
  • Flare monitors: thermal or visual sensors that detect whether a flare is lit and estimate flow.
  • Corrosion and methane sensors: increasingly common on gathering and processing equipment, driven by both cost and regulation.
  • Asset trackers: GPS-based trackers on rental equipment, trucks, and high-value hardware.

Midstream and downstream IoT is generally more mature, both because the stakes are higher (pipeline leaks, refinery incidents) and because the economics justify heavier instrumentation.

What IoT Is Good At

Where IoT delivers real value in oil and gas:

  • Continuous measurement on assets where continuous matters: high-rate wells, compressor stations, pipelines, refinery process equipment.
  • Exception-based management: alarms pushed to the right person when a variable goes out of range, reducing the need for constant human attention.
  • Geographic reach: sensors in remote locations where sending a human daily isn’t practical.
  • Regulatory compliance: continuous measurement required by emissions rules, flaring rules, or safety regulations.
  • Historical data for troubleshooting and optimization: understanding why a well started acting up by pulling the last 30 days of pressure history.

The common thread: IoT is worth it when the marginal cost of the sensor and telemetry is less than the marginal cost of the information it produces and the actions it enables.

What IoT Is Bad At

Where IoT falls short:

  • Wells where per-sensor pricing eats the budget. A $2,000 sensor on a low-rate well doesn’t pencil out. Flat-rate-per-site monitoring (unlimited sensors at that location) changes the math for operators with lots of sites.
  • Operations with poor connectivity. Cellular isn’t always available and satellite telemetry can get expensive fast. Gateways that auto-switch between cellular and satellite close the coverage gap.
  • Replacing judgment. A tank level sensor tells you the tank is at 78%. A pumper tells you the tank is at 78%, the stuffing box is leaking, and the gas line has a pinhole. The sensor doesn’t see what the pumper sees.
  • Standing in for a workflow. IoT data in a dashboard nobody looks at is no better than no data. The value is in the action, and the action requires a workflow.
IoT is valuable when the data turns into action.

For conventional wells where SCADA is breaking down or never got installed, TinyPumper is the drop-in remote monitoring layer: tanks, pressures, runtime. The producer owns the wells, owns the stack, and owns the call.

See how TinyPumper works →

How IoT, SCADA, and Production Apps Fit Together

There is confusion in the industry about where IoT stops and SCADA starts. The honest answer:

  • IoT devices are the sensors and connected gear at the asset. The “edge.”
  • Telemetry and connectivity is how the IoT data gets from the asset to somewhere useful.
  • SCADA is the aggregator and supervisory system that takes IoT device data, displays it, alarms on it, and stores history. SCADA can be thought of as “IoT with an operator in the control room.”
  • Production apps sit at the human workflow layer, capturing what the pumper sees and does, allocations, state reports, and exec dashboards. They pull in IoT and SCADA data too, so the producer has one screen for field-entered and sensor-sourced data.

All four layers can coexist, and many well-run operations use all of them. The mistake is thinking one replaces the others. IoT sensors don’t replace the pumper’s eyes on a leak; SCADA doesn’t replace a flare monitor; a production app doesn’t replace continuous measurement on the wells that need it. (For a layer-by-layer breakdown of the connected-sensor stack, see the oilfield IoT overview.)

Where Independent Producers Fit

For an independent producer (the operating company that owns the wells and signs the check), the IoT conversation usually boils down to two honest questions. First: which wells genuinely need continuous measurement? Second: which ones get covered by the daily pumper visit plus selective monitoring at the tank battery? Whether field work is done by company pumpers or by a contract pumping outfit is an implementation detail. The producer owns the call.

What actually happens on most independent books: SCADA already lives on horizontal or high-rate wells where the math worked. On the rest (conventional wells where SCADA either broke down over time or was always too expensive to justify) a SCADA alternative covers tank levels, pressures, and runtime. The pumper still visits to catch what sensors miss. The dashboard pulls it all into one screen.

TinyPumper is the SCADA alternative for that second bucket: conventional wells where SCADA doesn’t pencil. Roughly 99% of SCADA’s upside without the capex or complexity. Installs in 10 minutes, flat rate per site, unlimited sensors. The value prop holds at 50 wells and at 5,000. GreaseBook is the production app that ties daily pumper capture, state reports (TX, MS, AL, WY, MI), allocations, and dashboards together, and integrates with the SCADA you’re already running on the wells that warranted it.

The producer who gets value from IoT isn’t the one with the most sensors. They are the operator who decided, before buying anything, who owns the alarm, who opens the dashboard, and what decision changes because of the reading. That is identity, not an RFP line item.

Amateur vs Pro: How Operators Deploy Oilfield IoT

The amateur… The pro…
Orders 100 cellular sensors before checking signal at the lease Runs a site survey with an actual device before the first PO
Picks the vendor whose slide deck looked best Runs a 30-day pilot at three sites with different comms environments
Lets the data die in the vendor cloud portal Routes the alarm to the pumper’s phone before the sensor ever ships
Skips the pumper because “the sensor will see it” Treats the pumper and the sensor as two instruments with different jobs
Treats IoT as a one-time project Budgets for batteries, calibration, and firmware updates every year of the program

Wrong Fit for This Page

If you are researching IoT platforms for a large-scale upstream digital transformation program, talking to Deloitte, Accenture, or Cognizant, or building an RFP for a multi-field IoT rollout, this page is too ground-level. This page is for the independent producer trying to understand what IoT means for their actual operation and where it fits against other visibility tools.

FAQ

Is TinyPumper an IoT platform?

Yes, in the practical sense. TinyPumper is a matchbox-sized solar-powered gateway plus radar tank sensors and wellhead pressure sensors. The gateway pushes data to the cloud over cellular or satellite (auto-switching, 100% continental US coverage). Self-installs in about 10 minutes. It’s positioned as the SCADA alternative for conventional wells where the economics on SCADA never worked or where aging SCADA is breaking down.

What is IoT in oil and gas?

IoT in oil and gas is the network of connected sensors and devices (at wellheads, tanks, pipelines, and compressors) that collect data from physical equipment and send it to cloud platforms or SCADA systems for monitoring, alarming, and analysis.

What are the 4 types of IoT devices in oil and gas?

A common grouping: sensors and transmitters (pressure, level, flow, temperature), actuators and controllers (valves, pumps, RTUs), connectivity devices (cellular modems, radios, satellite modems), and edge compute devices (PLCs, gateways with local logic). All four appear in oilfield IoT deployments.

What are the 5 C’s of IoT?

The “5 C’s” framework commonly cited in IoT literature: Connect (devices and platforms), Collect (data), Communicate (the data somewhere useful), Compute (analyze it), and Collaborate (share insights across the organization). In oil and gas, the weakest link is usually the last two.

How does IoT improve oil and gas operations?

Through continuous measurement of assets, exception-based management, remote monitoring of assets in hard-to-reach locations, and regulatory compliance support. IoT works best when the data flows into a workflow that drives action.

About the author: Greg Archbald is the founder of GreaseBook. He built the product from inside the oil patch and has spent 15+ years on the operator side of oil and gas technology.

On conventional wells, SCADA is often either breaking down or was always too expensive to justify.

TinyPumper is the drop-in alternative. Solar-powered gateway, radar tank sensors, wellhead pressure, engine runtime. 10-minute self-install, flat rate per site, unlimited sensors, cellular + satellite auto-switching. Works at 50 wells and at 5,000.

See how TinyPumper works →
**P.S.** Most IoT pilots in oil and gas stall inside 18 months. Not because the sensors fail. Because nobody owns the data coming off them. Pick the owner before you pick the sensor.