Asset tracking systems

Asset tracking ties spatial data to the operational reality of infrastructure: where assets are, what condition they’re in, when they were last inspected, what’s been done to them. The difference between a static map and a system that keeps up with reality.

We deliver asset tracking systems for utility owners, network operators, and infrastructure managers. Geospatial work is delivered through our partner Geodars.

Why asset tracking is its own discipline

Most organisations have asset records of some kind — spreadsheets, file geodatabases, scattered drawings. The gap between that and a working asset tracking system is structural:

1. Asset records need typing. A “thing on a pole” isn’t useful. A “Class 4, 40-foot wood pole, installed 2019, joint-use with X telco” is.

2. Records need versioning. Knowing today’s state isn’t enough. You need to know what changed when, who changed it, what triggered the change.

3. Field data has to flow back. Asset records that don’t update from the field decay. The tracking system needs to be the path of least resistance for capturing inspection results, faults, and changes.

4. Reporting has to surface what matters. The system that needs a GIS analyst to extract a report isn’t a system, it’s a database. Reporting and dashboards make the data operational.

5. Integration with non-spatial systems matters. Work orders, finance, ERP — asset records that don’t connect to these stay siloed.

What’s in an asset tracking system

A complete delivery covers:

Data model

• Asset types and attributes
• Topology where applicable (parent / child relationships, network connectivity)
• Lifecycle states and event types
• Versioning approach

Field capture

• Mobile / tablet workflow for inspection, fault reporting, asset addition
• Offline-capable where field connectivity is unreliable
• Photo and GPS-logged data attachment
• Form design for the specific inspection processes

Backend

• Authoritative spatial database (typically PostGIS or SDE)
• Event store for asset history
• API for integration with other systems

Front-end

• Web GIS portal for desktop users
• Mobile / tablet apps for field use
• Reporting and dashboards for management

Integration

• Work-order system integration
• Finance / cost tracking
• ERP for capex and operational reporting
• Sensor data where applicable

Asset domains we work in

• Telecom networks — fibre, copper, splice closures, cabinets, OLT equipment
• Power utility — poles, transformers, substations, lines, switchgear
• Water utility — pipes, valves, meters, treatment equipment
• Fixed infrastructure — buildings, roads, structural assets
• EV charging — chargers, distribution, supply equipment

Each domain has its own data model conventions; we work to industry standards where they exist (ESRI Utility Network for utilities, OGC standards generally) and design where they don’t.

Inputs we need

A productive asset tracking engagement runs on:

• Asset domain — what kind of assets, how many, where
• Existing data state — what records exist now, in what format
• Operational workflows — how inspection, fault, replacement work today
• Integration points — what other systems need to connect (work orders, finance, ERP)
• User base — who’ll use the system, in what roles, on what devices
• Performance requirements — data volume, concurrent users, reporting expectations

Common pitfalls in outsourced asset tracking

Building before assessing data state. Asset tracking systems built over inconsistent legacy records expose every data quality issue immediately. We assess and where needed cleanse before deployment.

Field workflow ignored. A tracking system that field crews refuse to use stays empty. We design field workflow with field crews, not in isolation.

Reporting as a Phase 2. Dashboards delegated to “after launch” often never happen. We deliver reporting as part of the initial system, not after.

Integration as point-to-point. Asset systems built with brittle point-to-point integrations to other systems become maintenance liabilities. We build with proper APIs and considered integration patterns.

Typical timelines

• Single-domain, mid-size deployment — 8-16 weeks
• Multi-domain enterprise deployment — 16-32 weeks
• Large utility programme with full integration — 6-12 months

Asset systems usually evolve post-launch — we structure for that rather than treating launch as the endpoint.

How we deliver

Geospatial work runs through our partner Geodars. The team has direct experience with utility asset tracking, telecom network records, and infrastructure asset management at scale.

Talk to us about an asset tracking project

Tell us the asset domain, the existing state, the user base, and what integrations matter. We’ll scope, price, and discuss the right delivery approach.