Where Should Project Data Live? A Digital Model for Infrastructure Projects

Today, the greatest risk in infrastructure delivery isn't physical materials, but information: its location, control, and reliability. Every big project faces uncertainty about which system provides the real source of truth.

Infrastructure projects are no longer delivered with drawings and reports alone. They are delivered with living, evolving digital information.

As a result, owners and project leaders are increasingly asking a simple but important question: where should project data live? Not just during construction, and not just at handover, but across the full lifecycle of the asset.

Through our work with infrastructure teams across Canada, we have seen that the most successful organizations treat this as a design decision, not a technical afterthought. ArcGIS Project Delivery Subscriptions (PDS) support this by providing a practical, repeatable delivery model for how information is created, shared, and transitioned from delivery into operations.

Not All Data Has the Same Job

One of the most common pitfalls we see in digital delivery is the push to put everything into one system and then wondering why none of it quite works. In practice, different information exists for different purposes. Some supports how organizations work, some supports how the project is delivered, and some supports how the asset will be operated for decades.

Separating these concerns by design, while still allowing information to flow between them, is the foundation of a resilient digital delivery strategy.

We’ve found that once teams stop debating which system is “the system of record,” progress gets much easier.

Three Environments, One Connected Delivery Model

In practice, this leads to a simple but powerful model built around three connected environments. This model doesn’t replace design tools, document management systems, or construction platforms. It connects them through location.

The AEC organization’s ArcGIS environment is where delivery standards, templates, and repeatable workflows are developed and maintained. It is not a project system. It’s a capability system.

The Project Delivery Subscription environment is where the project itself lives digitally. This is the shared, governed space used by owners, designers, constructors, and field teams. It’s where field data capture, location-enabled inspections, issue tracking in context, reality capture, and a location-based, construction-phase digital twin actually live. It is intentionally separate from any single organization’s enterprise systems but connected to all of them.

The owner’s ArcGIS environment is the long-term system of record. This is where authoritative asset information, operational digital twins, and maintenance history ultimately live and are governed over the life of the asset.

Designed for Continuity, Not Handover

Anyone who has lived through a traditional digital handover knows how fragile that moment can be. A critical advantage of this model is that digital delivery does not require “transferring” data from one party to another. In this model, project environments act as systems of engagement during delivery, while owner environments remain systems of record over time.

Projects can be initiated in one environment, delivered through the shared project environment, and transitioned into operations by simply changing governance and access. The same information continues to live and evolve, but responsibility shifts as the project moves from delivery to operations.

Some data is created in the project environment and synchronized into owner systems. Some data remains in owner systems and is referenced throughout delivery. The result is continuity instead of handover, and far less risk at project closeout.

Removing Friction: Access Should Scale with the Project

Large projects involve many participants, and not all of them are GIS professionals. Field crews, inspectors, contractors, and oversight teams need access to information and simple applications, not complex systems.

Project Delivery Subscriptions are designed to make this easy. Teams can quickly bring new participants into the project environment, give them access only to what they need, and adjust or remove access as the project evolves. This matters because access delays often become delivery delays.

Just as importantly, access is tied to the project, not to any single organization’s internal systems. When the project winds down, the digital environment can be retired or transitioned cleanly.

A Practical and Proven Data Flow

In simple terms, delivery standards and patterns flow from organizational environments into the project. Day-to-day delivery data is created and managed in the project environment. And validated, operationally relevant information flows into owner systems.

What connects these environments is location. When project information is spatially enabled, it can move between systems without losing context.

Diagram showing data flowing between AEC Core ArcGIS, Project Delivery Subscription, and Owner ArcGIS.

Not all data moves. Not all data is duplicated. And not all data is meant to be permanent. This is not a limitation. It is what makes the model sustainable.

Digital Delivery Is a Design Decision

The most advanced organizations are no longer asking how to license software for a project. They are asking how to design digital delivery from day one.

When ArcGIS Project Delivery Subscriptions are used as a shared project environment, a construction-phase digital twin platform, and a bridge between delivery and operations, they become a foundational part of modern infrastructure delivery.

Final Thought

Digital delivery is no longer just about models and drawings. It is about governing living information across organizational boundaries.

When data architecture is treated as part of project architecture, digital delivery stops being a risk and starts becoming an advantage.

If your organization is planning upcoming projects or looking to modernize how digital delivery works across teams, Esri Canada can support that work. We work with owners and delivery organizations to design practical project data strategies and to apply Project Delivery Subscriptions in ways that reduce risk, improve coordination, and ensure project information continues to deliver value long after construction is complete.