If you run a rental or construction equipment fleet, you already know the uncomfortable truth about IoT: not everything is connected, and it probably never will be. OEM-fitted telematics on newer machines, third-party trackers on older assets, Bluetooth beacons on attachments and small tools — most hire fleets run on somewhere between five and twenty different telematics systems, each with its own portal, its own login, its own data format. And underneath all of them sits a layer of equipment with no sensors at all. That’s not a failure of your digitization program. It’s the normal, permanent shape of an asset-heavy fleet.
The problem isn’t the gap itself. It’s what most platforms do with it: they quietly draw a line around the connected assets, build workflows and dashboards for that subset, and leave everything else to spreadsheets, phone calls, and a yard walk. The result is a fleet operating on two disconnected sources of truth — one automated, one manual — and neither one tells you the whole story.
Workflows don’t care whether an asset is connected
Think about the workflows that actually run a rental or construction operation: dispatch and asset selection, preventive maintenance scheduling, contract and billing cycles, compliance and inspection tracking, damage and downtime reporting. Every one of these workflows spans the entire fleet, not just the instrumented portion of it.
Take utilisation — the number rental businesses live or die by. Finance measures it in revenue. The fleet manager measures it in run hours. The branch manager measures it in days on hire. None of those views are wrong, but none of them are complete on their own, and a utilisation report that quietly excludes the un-instrumented third of a fleet isn’t a utilisation report — it’s a partial one that looks complete. Perspio unifies all four dimensions — time on hire, revenue against potential, usage-based run hours, and downtime — into a single per-asset view, so the gaps between what a machine appears to be doing and what it’s actually doing surface immediately, not at month-end.
The same logic holds for dispatch. Asset availability shouldn’t be a manual status field someone remembers to update. Perspio pulls signal from wherever it exists — fault codes from telematics, but also inspection results, open operator tickets, and compliance status from systems that have nothing to do with IoT — and applies the same business rules across all of it to decide whether an asset is genuinely fit to go out the gate. A crane’s availability and a generator’s availability get evaluated on the same standard, whether the data behind that decision came from a sensor or a technician’s inspection form.
And even where connectivity is thin rather than absent, the platform is built to use what’s there. An asset without active telematics still has a last-known location from its most recent signal. Bluetooth beacons extend coverage to unpowered attachments that will never justify a full telematics install. Perspio doesn’t wait for perfect instrumentation before it becomes useful — it works with the connectivity that actually exists on a real fleet, and gets more precise as coverage improves rather than being blind until it does.
And “unconnected” isn’t only small unpowered gear. An older excavator or crane bought before telematics was standard is just as much a blind spot as a trailer that never had a sensor — and so is a newer machine whose OEM telemetry subscription quietly lapsed and nobody noticed, because that data feed was assumed to be permanent rather than managed. High-value equipment goes dark for the same reasons cheap equipment was never wired up in the first place.
The common industry answer to this problem is to sell you more hardware: put a battery-powered tracker on every trailer, generator, light tower, and compressor, and the visibility gap closes once the rollout is done. That’s not wrong, exactly — more coverage is always better — but it puts a capital project on the critical path to visibility, and still leaves you managing two data models until every last asset is instrumented. Our view is that instrumentation and operational visibility are separate problems. Your ERP, your workshop system, and your inspection platform already hold usage, condition, and compliance data on the assets that will never carry a sensor. Perspio’s job is to bring that into the same model as your telemetry today — not to wait for a hardware programme to finish first.
The construction and rental case for this
Rental and construction fleets are a particularly sharp example of why whole-fleet visibility matters. Fleets are mixed by necessity — new high-value equipment gets telematics from the OEM, older or lower-value units often don’t, and retrofitting an entire yard is rarely worth the cost. Compliance and inspections are frequently driven by regulation and contract terms rather than sensor data at all — vehicle safety checks, load certifications, pressure vessel certification. A platform that can’t bring inspection records and manual maintenance history into the same operational picture as live telemetry is asking teams to keep running two systems in parallel, which is exactly the fragmentation IoT investment was supposed to eliminate.
Operational risk follows the same pattern. Breakdowns, compliance lapses, and overdue returns tend to surface as reactive events — reported after they’ve already become incidents or disputes — because the underlying data lives in whatever system happened to capture it. Bringing that data into one view is the starting point, not the endpoint: business rules can then trigger the actual response — a work order raised, a stakeholder notified, a contract status updated — regardless of whether the triggering signal came from telemetry or a manual inspection.
Why this matters even more for industrial AI
This gap becomes a much bigger problem the moment AI enters the picture. We describe the value Perspio delivers in four progressive stages: Visibility — a single unified view of what’s happening across the fleet, with no manual aggregation. Suggestion — analysing that unified data against defined parameters to identify what action should be taken. Control — executing the action directly. Automation — codifying repeated patterns into fully automated workflows that close the loop without manual intervention.
Most platforms stop at stage one. But every stage past Visibility depends on the same thing: a dataset that actually represents the whole fleet. Predictive maintenance models, utilisation forecasting, breakdown pattern analysis — these all need to be trained and run against a representative dataset. If a model only ever sees the connected slice of a fleet, its suggestions are only valid for that slice, and the business decisions built on top of them inherit that blind spot.
You can’t run predictive maintenance across 60% of a fleet and apply the output to the other 40% by assumption. You can’t optimise dispatch or flag rotation imbalances with a model that has no visibility into a third of the inventory. Industrial AI is only as trustworthy as the completeness of the data underneath it — and in an asset-heavy business, completeness has to include the equipment that isn’t, and may never be, instrumented. This is why unifying telemetry with operational systems — ERPs, workshop platforms, inspection tools — isn’t a peripheral feature of Perspio. It’s the prerequisite for applying AI to the fleet at all, rather than to a demo-friendly subset of it.
What that looks like in practice
Customers running mixed fleets on Perspio describe this less as a dashboard problem solved and more as an operating model shift. As Ilsa Walsh of UpHire put it, not having to log into a different portal for trucks and a separate one for every other machine class was, in her words, genuinely exciting. Peter Davis, EGM Asset Services at Coates, has pointed to the operational benefit of a central view of the whole equipment operation available at the click of a button. And Allen Besseling, MD of Hire Express, has described access to all the relevant data on every asset in one system as something that’s really making a difference for the business.
None of those benefits come from instrumenting every last asset. They come from a platform that treats connectivity as an attribute of an asset, not a qualification for whether it belongs in the workflow — or the AI model — running on top of it.
Want to see how Perspio brings connected and non-connected assets into a single operational view? Get in touch to talk through your fleet.
