When your assets live in the field: telemetry, apps and maintenance

Some companies keep their value inside one building. Others have it scattered across the territory: plants, substations, sites, vehicles, equipment installed at customer premises. Energy producers, utilities, environmental services, maintenance contractors all share this shape, and with it a specific set of operational problems. The head office learns about the field through phone calls, spreadsheets and monthly surprises. Every asset class has its own vendor portal. Technicians drive around with paper work orders. Regulatory reports are assembled by hand at the end of the period, from fragments.

I have spent years building the digital side of a company with this exact shape, a fleet and hundreds of pieces of equipment spread across the territory included. The lessons travel well across sectors.

Telemetry belongs with the operational data

Most connected equipment already produces data: meters, sensors, trackers, control systems. The common condition is that each stream lives in the silo of its vendor, one portal per brand, one login per portal, and nobody looks at any of them. The step that changes the picture is joining telemetry with the operational records the company already keeps: which asset it is, where it is, which customer or site it serves, when it was last maintained. A reading that arrives tied to the asset registry becomes usable by planning, maintenance and billing. A reading that stays in a vendor portal remains a curiosity.

The field needs tools built for the field

Technicians working on remote sites need applications designed for their conditions: readable in sunlight, usable with gloves, able to work through a whole day of poor connectivity. The pattern that holds is offline-first with automatic synchronisation, the camera used as the main input for documents and readings, and error handling that stays on the system side. When the tool respects these constraints, paper starts disappearing from the vans. When it does not, paper returns within weeks, and the technicians are right.

Maintenance planned from numbers

With telemetry and field reports flowing into one place, maintenance stops being a calendar guess. Hours of operation, alarms, readings outside range and the history of past interventions can drive the schedule, and route planning can group interventions by area to cut travel time. The same data answers the questions that matter at the end of the month: which assets absorb the most work, which sites generate the most exceptions, where the next investment makes sense.

Reporting as a by-product

Regulated sectors carry reporting duties: production data, environmental records, safety documentation, grid or authority submissions. Assembled by hand, these reports cost days and carry errors. Generated from the operational flow, they become a by-product: the data was captured once, at the source, in the field, and the report is a query over it. This is the same principle I apply to compliance in general: obligations built into the digital process, documented by the systems themselves.

Common objections

"We already have SCADA and vendor portals." Good, they keep doing their job. The missing piece is usually the join between those streams and the operational records, which is where planning and reporting live. Integration is the work, and it leaves existing systems in place.

"Our sites have poor connectivity." That is a design constraint, and a manageable one: local buffering on the equipment side, offline-first tools on the human side, synchronisation when the link returns. The architecture is well understood.

"We are a small team." The approach scales down well: one asset class, one join with the registry, one field tool. Each step returns value on its own, and the next one rests on it.

What to take home

A quick self-assessment for any company with distributed assets: how many portals does it take to see the state of the field this morning? How does a reading travel from the site to the monthly report? How much paper rides in the vans? The answers usually point directly to the first process worth digitising.

Does your company run assets across the territory? Let's talk.