Remote monitoring lets a maker of hoists, cranes, compaction rollers, crushers or light towers see how every machine works on every job site, and that visibility supports two businesses at once: maintenance sold as a monthly plan that prevents stoppages, and rental or usage billing priced on real working hours. A hoist that reports 48 hours worked at $35 an hour invoices itself; the same data stream flags its brake for adjustment 57 hours before the problem stops the job.
This article covers both models with the mechanics and example figures behind them, plus how the machines connect and what to measure. The interactive walkthrough lives on the Heavy Equipment solutions page.
Key points
- Working hours are the product: totaled per machine, per site and per month, they become a rental invoice generated from telemetry instead of a paper log.
- Wear announces itself. In the page’s example, a hoist brake slipping 25% more than its adjusted baseline books its own service before a load ever drops.
- Everything in the category connects: crushers over Modbus, compaction and drilling rigs over LoRaWAN, hoists and cranes over cellular, light towers over satellite.
- Geofences answer the oldest question in the rental business: which site is the machine actually working on today.
From signals to decisions
Heavy equipment produces a short list of honest signals, and one pipeline turns them into both revenue streams:
The retrofit kit that produces those signals mounts without touching the OEM controller:
The full measurement set on the solutions page: operating hours, location and geofence, fuel level, motor temperature, brake lining, engine load and idle time, vibration, and load and tilt. Few machines need all eight; a light tower earns its keep with location, fuel and run hours alone.
How does the maintenance model work?
The page’s simulated walkthrough shows the pattern. Hoist H-12 works a viaduct site for a civil contractor. Its brake normally holds at the adjusted baseline of 2 mm of slip; one week, under the same loads, slip runs 25% higher and crosses the adjust limit. The platform adds a brake adjustment to the next scheduled visit and tells the site. The brake is adjusted, slip returns to normal, and the month closes with 130 operating hours, the uptime guarantee kept, and a $4,550.00 invoice issued on time.
The sellable part is what did not happen: no dropped load, no stopped gantry, no emergency callout. A maintenance plan priced per machine per month renews on exactly that record, and with a fleet reporting, trained analytics models learn each machine’s normal so the adjust limits stop being guesses.
How does the rental model work?
Hours are totaled by an Analysis script, per machine, per site, per month, and posted to your billing system over HTTP. In the simulated account, one hoist bills 48 hours at $35 an hour ($1,680 for the month so far, 12% over October), and the four-hoist fleet stands at $6,615 ready to bill, with each unit’s hours and site listed: $1,365 for 39 hours at a harbor job, $2,030 for 58 hours at a depot, $1,540 for 44 hours at a precast yard.
Two details make the model honest. Geofences confirm which site each machine worked, because machines have a habit of migrating to jobs they were never billed to. And idle-time data prices the next contract: a fleet that idles 40% of the day is a fleet you can shrink, or a rate you can sharpen, and only the maker with the data knows which.
What hardware goes on the machine?
Rugged cellular routers and gateways, such as those from Digi International, bridge CAN or Modbus from the machine and backhaul over LTE; battery-powered LoRaWAN trackers cover attachments and assets with no power of their own; satellite covers the light tower on a remote right-of-way. On the platform side, more than 500 integrated devices decode out of the box, and a payload parser handles any proprietary controller format as messages arrive.
Mining and heavy industry already run this pattern on TagoIO: Lynkz Instruments built custom monitoring that cuts downtime in mining operations, and SKOMUNIKACJA delivered a smart factory for a coal mine.
The business models, priced
| Model | What the customer pays for | Basis |
|---|---|---|
| Maintenance plan | Jobs that do not stop | $ per machine, monthly |
| Usage billing | Hours actually worked | $ per operating hour |
| Fleet intelligence | Utilization, idle share, fuel per hour across sites | $ per fleet subscription |
| Output contracts | Tonnes crushed, nights illuminated | $ per unit of output |
Each row funds the next, a progression we unpacked in Climbing the Fusion Ladder; the short version is that the models lower on the table need the meters and the trust the earlier ones build.
Who sees what: maker, dealer, contractor
The data carries three audiences, in layers. Your engineering and product teams see the whole installed base in TagoIO: duty cycles by model, failure precursors by component, utilization by region, the fleet knowledge that, as we argued in What Makes a Moat in IoT, no competitor can synthesize without owning the machines. Each dealer or rental branch sees its own territory: the machines it services, the visits coming due, the hours ready to invoice. And each contractor opens a portal under your brand showing their sites, their machines, their hours and their invoices. Access Management policies keep the layers isolated; TagoRUN with the Custom Domain & Whitelabel and Custom Mobile App add-ons puts your name on every screen, including the one in the site foreman’s pocket.
One practical note on alerts: a job site does not read dashboards. The alerts that matter go out as push notifications, SMS or email to the people who act on them, and every alert that books a service visit leaves a record your renewal conversation can stand on.
Frequently asked questions
Can machines already in the field be connected? Yes. Add-on trackers and sensors for location, operating hours, temperature or vibration retrofit over cellular, satellite, LoRaWAN or other supported networks. New machines send from the controller over MQTT or HTTP.
Our controller speaks its own format. Does that block us? No. A payload parser converts it into named variables as each message arrives.
Can each contractor see only their own machines? Yes. Access Management policies isolate every customer in their TagoRUN portal, which runs under your brand with the Custom Domain & Whitelabel add-on and as your own app with the Custom Mobile App add-on.
Can we bill working hours without changing our billing system? Yes. An Analysis totals working hours, idle time or uptime and sends the figures to your existing system over HTTP.
Is the platform solid enough for rental invoicing? TagoIO runs on AWS in the US or the EU with a 99.9% uptime SLA for eligible accounts, ISO 27001 certified and GDPR compliant. Details at tago.io/trust.
Start with one machine on one job
Connect a single hoist or roller on a cooperative customer’s site, let it report for a month, and put two numbers side by side: the hours it worked and the service visit it booked itself. That page of data is the rental pitch and the maintenance pitch in one. The Heavy Equipment solutions page walks the full build, and the free Building Smarter Equipment Monitoring Systems ebook covers the architecture decisions underneath.