Remote monitoring lets a maker of gensets, UPS systems, battery storage or EV chargers see every unit at every customer site, catch the failures that cause failed starts days in advance, and bill for proven readiness instead of selling hardware once. The models in use today run from a monthly monitoring plan per machine, through standby availability billed by the hour, up to metering the energy or charging sessions the equipment delivers.
This article covers what those models look like with real mechanics and example figures, how the machines connect, and which measurements carry the business. The interactive version of the examples lives on the Power Generation solutions page.
Key points
- Standby power can be billed monthly because readiness is measurable: battery voltage, fuel, coolant temperature and transfer-switch state, checked continuously and reported as availability.
- The failure that matters most, a genset that does not start, announces itself early as a battery drifting below float. Early warnings make the availability guarantee safe to sign.
- Everything in the category connects: UPS and rectifiers over Modbus, EV chargers over LoRaWAN or Sigfox, gensets over cellular, battery storage and solar over satellite where coverage ends.
- Billing runs on the same telemetry: an Analysis totals hours ready, run hours or energy delivered per customer per month and posts the figures to your billing system over HTTP.
Why standby equipment suits recurring revenue
A standby genset is bought for the hours it does not run, which makes it the rare machine whose value is invisible until the worst moment. The owner cannot tell a ready genset from a doomed one by looking at it; the maker, with telemetry, can. That asymmetry is the business: the manufacturer is the only party able to prove, continuously, that the investment will work when the grid fails. Proof has a price, and it renews monthly.
The same logic covers the rest of the category: diesel and gas gensets, portable and standby generators, mobile power units and light towers, inverters, UPS systems, rectifiers, battery energy storage and voltage stabilizers, EV chargers, and solar and CHP hybrid units.
How do generators, UPS and chargers connect?
Each machine reports over the network its site already has, and the platform receives all of them the same way:
On the solutions page the groupings look like this: UPS, inverters and rectifiers report over Modbus from their controllers; EV chargers over LoRaWAN or Sigfox; gensets and mobile power over cellular, MQTT or HTTP; battery storage and solar over satellite where no tower reaches. Satellite stopped being exotic this year: TagoIO receives NB-NTN traffic through Skylo, with LooUQ hardware, over TagoTiP, so the genset behind a rural substation reports into the same account as the hospital unit downtown.
Units already in the field retrofit with add-on sensors for battery voltage, fuel level, temperature or location, with no change to the controller. Proprietary controller formats pass through a payload parser that converts each message into named variables on arrival.
Which measurements carry the business?
| Measurement | What it proves | What it bills |
|---|---|---|
| Battery voltage and charging power | The unit will start | Availability by the hour |
| Fuel level | It will keep running | Refueling service, theft alerts |
| Run hours and frequency | Exercise cycles happened | Maintenance by condition |
| Coolant temperature | Cooling is healthy | Early fault service |
| Electrical load | What the site actually draws | Capacity planning, energy billing |
| State of charge | Storage is ready to dispatch | Peak-shaving contracts |
A failed start, prevented: the walkthrough
The solutions page walks a simulated case worth retelling in numbers. Genset S-07 backs up the east annex of a hospital, and its maker bills the hospital by the week for every hour it stands ready to start. Its battery sits on float at 27.2 V, the reference for ready. One week the voltage drops 1.6 V under float, past the early-warning line but short of critical failure: the signature of a dying battery charger, the single most common cause of failed starts. A charger check joins the next scheduled visit, the site is notified, the new charger goes in, and the battery returns to float. The week closes at 100% uptime, the availability guarantee stays kept, and the week’s bill, $294.00 for that unit, goes out as planned.
Scale the picture up and the fleet view does the selling: in the simulated account, 272 hours of standby so far this month bill at $1.75 an hour, one genset out of four needs attention, and the fleet total stands at $1,904 ready to bill. The mobile cards show the same model on other equipment: a UPS carrying an 86 kW load, 86% of its N+1 capacity, for $340 a month, and a battery system holding 62 kW off the site’s peak for $520 a month.
The business models, priced
| Model | What the customer pays for | Basis |
|---|---|---|
| Monitoring and service plan | Failed starts prevented, visits by condition | $ per machine, monthly |
| Standby availability | Readiness, proven daily | $ per hour on standby |
| Energy and sessions | Output delivered | $ per kWh or per charging session |
| Fleet benchmarks | Battery life and fuel per kWh across sites | $ per site subscription |
The progression between these models is the fusion ladder we described in Climbing the Fusion Ladder: each one moves more revenue from the day of sale to every month after it, and each one needs the telemetry of the model before it.
How does the billing actually work?
TagoIO measures; your billing stays yours. An Analysis script totals, per customer and per month, whatever the contract defines: hours ready, run hours, or energy delivered, and posts the figures to your billing or ERP system over HTTP. The invoice, the availability record behind it, and the alert history that proves the service happened all come from one data stream, which is what makes an availability guarantee auditable at renewal instead of negotiable.
Customers see all of it in a portal built with TagoRUN, each one isolated to its own machines by Access Management policies, under your domain with the Custom Domain & Whitelabel add-on, and in your own app on the App Store and Google Play with the Custom Mobile App add-on.
What about the thousands of units you already shipped?
Retrofit them, because they are the asset a competitor cannot touch. A cellular gateway wired to the controller covers the modern units; battery voltage, fuel level and temperature sensors cover the older ones that predate digital controllers, installed in an afternoon per site. Every retrofitted unit adds to the fleet record that prices your availability contracts, and that record compounds: battery life by climate, fuel burn by load profile, charger failure rates by model year. As we argued in What Makes a Moat in IoT, the installed fleet plus the data it generates is the part of a power equipment business that cannot be copied by shipping a better alternator.
Where does TagoAI fit?
TagoAI builds the fleet views so your engineers stay on the machines. Describe what you need in the TagoAI panel, for example “a standby fleet board that stays quiet while batteries sit on float and flags any genset that drops off it”, and TagoAI creates the widget and its code against your live devices. In the example on the solutions page, it flags the one genset off float at 25.1 V across the fleet. Verify what it builds against device data before customers see it; the point is that the dashboard that used to be a development ticket becomes an afternoon.
Frequently asked questions
Can units already installed be connected? Yes. Add-on sensors for battery voltage, fuel level, temperature or location retrofit over cellular, satellite, LoRaWAN or other supported networks. New machines send straight from the controller over MQTT or HTTP.
Our controller has its own data format. Is that a problem? No. A payload parser converts your format into variables as each message arrives.
Can we bill for standby or energy without replacing our billing system? Yes. The platform totals the hours or kWh and sends the figures to your existing system over HTTP.
Is the platform dependable enough to put in a contract? 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. Details at tago.io/trust.
How fast can we see our own fleet? TagoAI builds the first dashboards from a description; in the page’s example it flags the one genset off float at 25.1 V across a four-unit fleet. Verify its output against device data before customers see it.
Start with the machine that scares you most
For most makers that is the standby genset and its charger. Connect twenty units, run readiness checks for sixty days, and bring the prevented failed starts to your five best customers with an hourly price attached. The Power Generation solutions page walks the full path, and the free ebook Building Smarter Equipment Monitoring Systems covers the architecture underneath. A generator is insurance; connected, it is insurance you can prove, and proof is what customers renew.