# IoT for Compressor and Pump Manufacturers: How to Monitor Machines Remotely

> How compressor, pump, blower and vacuum makers connect new and installed machines, pick the measurements that matter, and bill air, flow or uptime monthly.

![IoT for Compressor and Pump Manufacturers: How to Monitor Machines Remotely](https://tago.io/og/blog/iot-for-compressor-and-pump-manufacturers.png)

IoT lets a compressor, pump, blower or vacuum manufacturer see every machine it ever shipped, running at every customer's site, in one place. New units report straight from their controller over MQTT or HTTP; installed units take an add-on sensor without opening the controller. Once the machines report, the manufacturer can sell monitoring and service plans, benchmark energy use across its whole installed base, and ultimately bill air, flow or uptime by the month instead of selling hardware once.

This guide covers the full path for fluid and air equipment makers: which machines can be connected, how the data gets out of the machine, which measurements carry the business, how predictive maintenance works in practice, and what the four revenue models look like, with the concrete mechanics behind each one. It expands on the [Fluid & Air solutions page](https://tago.io/fluid-and-air), where an interactive version of the examples below lives.

**Key points**

- Any fluid or air machine can be connected: new units through their controller, installed units through retrofit add-on sensors, with no change to the machine.
- Eight measurements cover most of the category: pressure and vacuum, flow, temperature, vibration, motor current and power, run hours and starts, oil and filter condition, levels and leaks.
- A clogged inlet filter announces itself as extra power drawn for the same air delivered, days before anything stops. That early warning is a sellable service plan.
- The end state is billing the output: air by the cubic meter, with pressure or vacuum uptime guaranteed in the contract. The invoice is computed from the same telemetry that runs the service plan.

## What is IoT remote monitoring for compressors and pumps?

IoT remote monitoring means every machine a manufacturer ships reports its operating data, such as pressure, flow, power draw and run hours, over a network to a cloud platform, where the manufacturer and its customers can see it live, receive alerts, and act on it. For the customer, it answers "is my air supply healthy and what does it cost me?" For the manufacturer, it turns a shipped product into a long-term data relationship.

The category is wide, and the approach is the same across it. On the compressed air side: rotary screw, reciprocating and scroll air compressors, portable and skid-mounted compressors, vacuum pumps, blowers and fans. On the liquid side: centrifugal, positive-displacement, diaphragm, submersible and booster pumps, along with dewatering, slurry, dosing and metering pumps. If it moves air, gas or liquid and has a motor, it can report.

![A towable compressor, the kind of machine that leaves the factory and reports back over cellular from any site](https://tago.io/images/sectors/fluid-and-air/towable-compressor-600.webp)

## How do you connect a compressor or pump to the cloud?

There are two paths, and most manufacturers run both at once.

**New machines connect through the controller.** Modern compressor and pump controllers already measure what matters and usually expose it over Modbus. From there the data travels over whatever network the site has: an industrial cellular gateway (rugged routers such as those from Digi International are a common choice), plant Ethernet speaking MQTT or HTTP, or a satellite link for machines past cellular coverage. If your controller speaks a proprietary format, a payload parser converts it into named variables as each message arrives, so readings are ready for dashboards, Analysis scripts and alerts without firmware changes.

**Installed machines take a retrofit kit.** An add-on sensor for pressure, current, vibration or temperature mounts on the machine and transmits over LoRaWAN, Sigfox or cellular, without opening the controller of a unit that left your factory years ago. TagoIO lists more than 500 integrated devices with ready-made decoders, so the sensor you pick almost certainly reports without custom code.

| Network | Best fit on fluid and air equipment |
| :---- | :---- |
| Modbus (RTU/TCP) | Reading the controller on new or recent machines |
| MQTT / HTTP | Units with an internet-connected controller or edge gateway |
| Cellular | Portable and skid-mounted compressors, rental fleets, sites without IT involvement |
| LoRaWAN | Retrofit sensors across a plant or yard; years of battery life |
| Sigfox | Low-rate retrofit points where coverage exists |
| Satellite | Dewatering pumps, remote boosters and quarry units beyond cellular |

## Which measurements matter on fluid and air equipment?

Eight measurements cover most machines in the category, and each one maps to a business purpose:

| Measurement | What it tells you | What it sells |
| :---- | :---- | :---- |
| Pressure and vacuum | The product itself, delivered or not | Uptime guarantees, out-of-band alerts |
| Flow | Output volume per customer | Billing per cubic meter |
| Motor current and power | Energy cost per unit of output | Efficiency programs, filter alerts |
| Temperature | Cooling and lubrication health | Early fault detection |
| Vibration | Bearings, alignment, cavitation | Predictive maintenance plans |
| Run hours and starts | Duty cycle and service clock | Service scheduling, rental billing |
| Oil and filter condition | Consumable state | Consumables on subscription |
| Levels and leaks | Tanks, sumps, seal health | Compliance and loss prevention |

You rarely need all eight on one machine. A dosing pump earns its keep with flow and run hours; a large rotary screw compressor justifies the full set.

## How does predictive maintenance work on a compressor?

Predictive maintenance on fluid and air equipment is mostly ratio-watching: output against input, compared with the machine's own baseline. The walkthrough on the solutions page (with simulated data) shows the pattern on a single machine.

Compressor C2 runs at a food plant, delivering line pressure at 6.8 bar. One week, it starts drawing more power to deliver the same air. Nothing has failed and nobody at the plant has noticed, but the platform compares every reading with C2's clean-filter draw of 31.5 kW, and when the draw runs 5% over it, it flags the signature of a clogging inlet filter. The system adds a filter swap to the next scheduled visit and notifies the plant. The filter is changed, power returns to baseline, the uptime guarantee in the contract stays kept, and the month closes with the invoice issued as planned, $3,801.60 in the simulated example.

![Dashboard view of the Compressor C2 walkthrough: motor power climbs through the week until it crosses the 33.1 kW swap limit, 5% over the 31.5 kW clean-filter draw, then falls back after Friday's filter swap; side stats show 6.8 bar line pressure, the guarantee kept, and the $3,801.60 invoice](https://tago.io/images/blog/iot-for-compressor-and-pump-manufacturers/compressor-filter-clog-dashboard.svg)

Two details make this work at fleet scale. First, the thresholds are not guesses: with hundreds of machines reporting, [trained analytics models](https://tago.io/analytics) learn each unit's normal and flag drift without hand-tuned limits. Second, detection is wired to action: on TagoIO, an alert can open a ticket, schedule the visit, and message the customer in the same flow, so the insight does not die on a dashboard.

## How can a manufacturer earn monthly revenue from connected machines?

The book [Fusion Strategy](https://store.hbr.org/product/fusion-strategy-how-real-time-data-and-ai-will-power-the-industrial-future/10689) (Govindarajan and Venkatraman, Harvard Business Review Press, 2024) describes four rungs a machine maker can climb, and our post [Climbing the Fusion Ladder](https://tago.io/blog/climbing-the-fusion-ladder) applies them to IoT businesses. On fluid and air equipment, the rungs are unusually concrete:

![From selling compressors to selling air: the four rungs priced, from a one-time machine sale to air billed per cubic meter](https://tago.io/images/blog/iot-for-compressor-and-pump-manufacturers/fluid-air-business-model.svg)

**Rung 1, Fusion Products: the machine, now connected.** Compressors, pumps and blowers that report pressure, flow and run hours. Still priced as one sale, but every unit shipped starts feeding the data that funds the rungs above.

**Rung 2, Fusion Services: the machine plus a paid service plan.** The clogged-filter catch above, sold monthly per machine. This is where most hardware makers stall, usually because the first plan was priced as a cost instead of a product. The plan is not "we watch your machine"; it is "your line does not stop and your filter is changed before it costs you energy".

**Rung 3, Fusion Systems: what your whole installed base learns.** With fleets reporting from many customers, you can tell each plant its energy per cubic meter of air and how that compares with similar sites you serve. Compressed air is one of industry's most expensive utilities, and leaks and inefficiency quietly consume a large share of it. A benchmark drawn from your own installed base is a subscription nobody else can sell, because nobody else has the data. This fleet knowledge is also, as we argued in [What Makes a Moat in IoT](https://tago.io/blog/what-makes-a-moat-in-iot), the part of your business a competitor cannot copy.

**Rung 4, Fusion Solutions: the result, billed every month.** The customer stops buying a compressor and starts buying air: so many cubic meters delivered, at a contracted rate, with pressure or vacuum uptime guaranteed. In the simulated fleet on the solutions page, one quarry unit has delivered 18,113 m³ so far in November at $0.018 per m³. You keep ownership of the machine; the customer trades a capital purchase for a metered utility; and your revenue renews for as long as the plant breathes. This is where to aim, and the earlier rungs are how you get the metering, the reliability record, and the customer trust to offer it.

## How do you actually bill for air, flow or uptime?

The platform measures; your billing stays yours. An Analysis script totals, per customer and per month, whatever the contract defines: cubic meters of air delivered, hours inside the agreed pressure band, or uptime percentage. It then posts those figures to your billing or ERP system over HTTP. The simulated examples on the solutions page show the range of models this supports: a booster pump billed flat at $180 a month, a vacuum unit on a $210 monthly oil-change plan timed by run hours rather than the calendar, and the per-cubic-meter quarry contract above. The meter, the evidence, and the invoice all come from the same data stream, which is what makes an outcome contract auditable instead of an argument at renewal time.

## What do your customers see?

Their machines, and nothing else. Each customer signs in to a portal built with TagoRUN and sees only their own units, service visits and plan, enforced by Access Management policies set by user, by tag, or for everyone. With the Custom Domain & Whitelabel add-on the portal runs on your domain under your brand, and the Custom Mobile App add-on puts your app, with your name, on the App Store and Google Play. For a manufacturer, that last detail matters more than it sounds: the monthly invoice arrives from the same brand the plant manager opens on their phone every morning.

## Where does TagoAI fit?

TagoAI builds the interfaces so your engineers stay on the machines. Describe what you need in the TagoAI panel, for example "a rental fleet dashboard, one tile per compressor, quiet while working pressure stays between 6.5 and 7.0 bar, highlighted outside it", and TagoAI creates the widget and its code against your live devices. In the example on the solutions page, four compressors report working pressure and the widget flags the one unit sitting at 7.2 bar with a note to check the regulator. Verify what it builds against device data before customers see it; the point is that a fleet view that used to be a development ticket becomes an afternoon.

## Frequently asked questions

**Can machines already installed in the field be connected?** Yes. Add-on sensors for pressure, current, vibration or temperature retrofit a machine over LoRaWAN, cellular or other supported networks, with no change to its controller. New units send straight from the controller over MQTT or HTTP.

**Our controller has a custom data format. Does that block us?** No. A payload parser converts your format into named variables as each message arrives, so the readings work in dashboards, analyses and alerts immediately.

**Can each customer see only their own machines?** Yes. Access Management policies control which dashboards each TagoRUN user sees. Multi-tenant isolation is the default pattern for OEM deployments.

**Is the platform reliable enough to bill on?** TagoIO runs on AWS in the US or the EU with a 99.9% uptime SLA for eligible accounts, is ISO 27001 certified and GDPR compliant, and encrypts data in transit and at rest. Details are at [tago.io/trust](https://tago.io/trust).

**How much does it cost to start?** Nothing. Connect the first machine on a free account, or [request a demo](https://tago.io/request-demo) and walk through it with an expert.

## Start with one machine

Every manufacturer that now bills for air started with a single connected unit. Pick one machine model and one customer who already calls you when it breaks, connect it, and run the monitoring for a quarter; the data will price rung two for you. The [Fluid & Air solutions page](https://tago.io/fluid-and-air) walks the whole path interactively, and the free ebooks [Building Smarter Equipment Monitoring Systems](https://tago.io/ebooks/equipment-monitoring-systems) and [Building IoT Solutions](https://tago.io/ebooks/building-iot-solutions) cover the architecture decisions underneath.

The machines you shipped last year will run for another decade. Connected, they report every cubic meter they deliver. The only open question is whose invoice that volume appears on.

[llms.txt](https://tago.io/llms.txt)
