ArcGIS Pipeline Referencing: turning pipeline network data into business value

That is why creating a single source of truth, where spatial data is accessible to stakeholders across the organisation, is so important. ArcGIS Pipeline Referencing (APR) is Esri's solution based on linear referencing, and a good foundation for asset data management related to linear assets. It is much more than a specialist GIS solution for pipeline operators: it creates a reliable foundation for managing routes, events and related information consistently within the ArcGIS platform. For organisations that depend on pipeline assets, this is not only about producing maps, but about creating confidence that engineering, operations, inspection and other teams all work from the same trusted understanding of the network.

Although APR is designed with the pipeline domain in mind, the underlying principle is relevant to many organisations that manage linear assets. Electric transmission operators managing underground cables, highway authorities planning construction and maintenance, and railway organisations managing track-related assets all face similar questions: how do we reference assets, events, conditions and work activities along a line in a consistent way? The terminology may differ by sector, but the need for reliable linear asset information is very similar.

Like utilities, pipeline operators are under constant pressure to modernise: they need up-to-date insight into ageing infrastructure, reliable inspection and integrity data, and the flexibility to support new operating models. The same is true for many organisations managing other linear infrastructure. In that context, location referencing becomes a strategic capability. If a valve, inspection anomaly or condition score cannot be linked reliably to the correct route and measure, downstream processes become harder, from analysis and reporting to risk assessment and maintenance planning.

APR helps organisations move away from drawing-centred or file-based ways of working towards a managed, enterprise-ready model for linear asset information. The real value is that APR can become part of the broader data backbone of the organisation, not another standalone database, but a governed capability that supports applications, analytics and business integration wherever assets and events need to be understood along a line.

One of the reasons APR is strategically interesting is its position inside the ArcGIS platform. It works with ArcGIS Pro for professional editing and data management, ArcGIS Enterprise for services and web access, and web applications for event editing and data consumption. This means pipeline referencing does not have to remain hidden in a specialist environment, it can become part of the same platform used for operational dashboards, field workflows, enterprise integrations, analytics and stakeholder communication.

In our projects, we often see that this is where the discussion becomes really valuable. The question is not simply how to implement APR, but what role location-referenced data should play in the wider application landscape. With the right architecture, APR becomes a reusable service layer that supports asset management, inspection, integrity and reporting systems well beyond the GIS department.

This connects to a point that is becoming more relevant with every discussion around AI and data-driven operations: data quality is no longer only a GIS concern. As a domain-specific solution, APR contributes by managing assets, events and condition information in a structured way against the right pipeline routes and locations, creating a trusted foundation for critical business decisions. That value is only fully realised when the data is also well-described: metadata at layer and attribute level helps people and systems understand what data exists, what it means and how reliable it is, making it easier to discover and apply elsewhere in the organisation. This matters increasingly for AI-driven operations too, since AI can only support meaningful insights when it can work with high-quality, well-described and context-rich asset data. For a pipeline or network operator, that foundation is not a technical nice-to-have, it is the backbone for safer operations, decisions and future innovation.

APR and ArcGIS Utility Network solve related but different problems. Utility Network manages connected utility infrastructure, connectivity, containment, network rules, subnetworks and tracing. It is highly relevant for distribution networks such as water, electricity, gas, district heating and telecom. APR focuses on linear referencing: routes, measures and events along linear assets, making it particularly relevant for transmission pipelines and other organisations that need a strong route-based view of their infrastructure.

Many organisations do not fit neatly into one category: some operate distribution networks, some transmission networks, and some a mix of both. In those cases, APR and Utility Network complement each other, supporting both the connectivity-based and route-based view of the network. That combination is especially powerful when organisations want to modernise their asset data without losing the operational knowledge embedded in existing processes.

At Avineon Tensing, we have made a clear choice to specialise in the Esri platform. Over the years, we have supported network operators across Europe with GIS strategy, data modelling, data migration, platform configuration, solution design, hands-on training and integration with other business systems. What I have learned in these projects is that success is rarely determined by technology alone: the real work is in translating operational knowledge into a maintainable data model, a realistic migration approach and workflows that users can trust.

That is also why we strongly believe in configuration over customisation. Some organisations have built highly specific GIS solutions over time because standard capabilities were not yet mature enough, but custom components are expensive to maintain, need to stay compatible with future releases, and often depend on external specialists for small changes. With everything Esri has added in recent releases for pipeline and network management, there are often new platform capabilities that can replace custom logic or simplify existing ways of working, and part of our role is helping clients unlock that and use the platform as it was designed to.

Knowledge transfer is part of our DNA too, and for me that works both ways: we bring technical expertise in ArcGIS, APR, Utility Network and data migration, while the organisation brings the operational knowledge that determines how a solution works in practice. Combining those perspectives, and staying close to Esri's roadmap instead of building custom, is what positions organisations to adopt new capabilities faster, with less friction and lower long-term dependency.

Case studies from our clients

Avineon Tensing obtained the ArcGIS Pipeline Referencing Specialty earlier this year. This specialty reflects our capability to support organisations that want to implement APR within ArcGIS Enterprise and modernise their pipeline system of record. We are currently the only certified APR specialty holder in Europe, which I am proud of, not as a badge in itself, but because it reflects years of practical experience and focus in this domain.

Avineon Tensing also holds the Esri Network Management Specialty for Utility Network implementations, and the combination matters: it means we can support clients in distribution, transmission or hybrid environments, and help them make the right architectural choices when APR and Utility Network both have a role to play. Whether the challenge is data migration, platform configuration, application integration, data model design or long-term governance, our focus is on helping clients move from technology potential to operational value.

A successful APR or Utility Network implementation should not start with software alone. Too often, these projects end up in deep technical discussions about how to recreate existing patterns and ways of working, understandable since those processes have grown out of real operational needs, but modernisation should also be an opportunity to challenge them. Which processes depend on accurate route information? Which assets, events and condition records need to be managed along a line? Which systems need to consume or update that data? Where is the source data strong, and where does it need improvement before migration? And which custom workflows should be preserved, and which replaced by standard platform capabilities?

When those questions are addressed early, APR can deliver value well beyond the GIS department: reducing data ambiguity, strengthening collaboration between GIS and engineering teams, and providing a future-ready foundation for analytics and decision-making. Sometimes the best solution is not to rebuild an old workflow in a new platform, but to change the way of working so the organisation can use reliable asset and network data more effectively elsewhere. For organisations preparing for hydrogen readiness, network repurposing or data/AI-driven operations, that foundation is becoming increasingly important.