ViewPro

Digital Twin + AR: How Cities Envision Utility Coordination with AR for Everyday Use

Written by ViewPro | Jun 8, 2026 12:21:59 PM

 

 

How do you manage that you cannot see? 

In the first blog of this series, Highland Park used Digital Twin + AI to bring the building facades closer to the real world.                    

In the second blog, the city applied the same thinking to the transportation corridors, using LiDAR, ArcGIS Pro, CityEngine, Terrain, Street imagery, and AI-assisted sign texture to make freeway corridors easier to understand in 3D.

The final story moves from the web scene into the field.

Utilities are some of the most important assets a city manages, but they are also among the hardest to understand in the real world. Water mains, sewer mains, devices, open channels, and 3D utility features are often buried, layered, or invisible during field coordination. On a desktop map, these assets may be clear to GIS specialists. On a job site, in a meeting, or during interdepartmental coordination, the same information can be harder to interpret.

That is where Digital Twin + AR becomes powerful.

The prototype explores how a configured Esri WebScene can be brought into a mobile augmented reality experience. The app lets users view utility layers in two modes: real-world AR for field-style viewing and tabletop AR for planning, meetings, and quick spatial understanding.

This is not about replacing survey, engineering design, or utility locating. It is about making the 3D utility context easier to see, discuss, and coordinate.

From Digital Twin to Field View

A digital twin becomes more valuable when it can travel.

Many city teams already work with web maps, web scenes, dashboards, and GIS layers. These tools are powerful, but they usually live on a screen. AR adds a different kind of access: it lets users bring the web scene into the physical space around them.

For this prototype, the app is configured with utilities sample data and can be reconfigured for other web scenes once the target web scene is ready. That makes the architecture reusable. The mobile app does not need to be rebuilt from scratch for every city or project. The web scene becomes the configurable mission source.

The app experience is intentionally simple:

  • Authenticate the user
  • Load the configured web scene
  • Display the mission screen
  • Let the user choose between real-world AR and tabletop AR
  • Provide layer controls
  • Support heading, elevation, and basemap adjustments
  • Let users inspect the 3D utility scene in a more intuitive way

The AR Mission is configured with layers including sewer mains, water mains, water devices, sewer devices, open-channel layers, and 3D utility layers. These are exactly the kinds of assets that benefit from visual context.

The ESRI Foundation: ArcGIS Maps SDKs for Mobile AR

The mobile AR app uses Esri's ArcGIS Maps SDKs for Swift and Kotlin. This matters because the app is not a separate visualisation disconnected from the GIS system. It is built around the same web scene concept that GIS teams already understand.

For iOS, ArcGIS Maps SDK for Swift supports AR scene experiences that can display geographic content in augmented reality. For Android, the ArcGIS Maps SDK for Kotlin supports similar AR scene workflows. Together, these SDKs allow the mobile experience to serve both major mobile platforms while staying connected to Esri web scene content.

The design follows two useful AR patterns:

  • Real-world AR mode: The scene is positioned around the user's real environment, based on the device's location, heading, and elevation.
  • Tabletop AR mode: The scene is placed as a scaled 3D model on a physical surface, useful for office review, stakeholder meetings, and quick planning conversations.

This two-mode structure is important because field coordination and planning coordination are different jobs. A field user may need to see how utility information relates to their physical location. A planner, engineer, or manager may need a compact city-scale view on a table before discussing a work area.

The Mobile Workflow: How the App Works

1. Authentication and Mission Entry

The app begins with a mission entry screen. Users can sign in or enter the configured mission depending on the authentication setup. This gives the city flexibility to support anonymous access for demonstration environments or authenticated access for controlled operational use.

The mission screen confirms the configured location and scene context. In the screenshots, the app identifies the AR Mission and indicates that the 3D global web scene is ready.

2. Loading the Configured Web Scene

Once the mission opens, the app loads the configured web scene. The web scene is the source of the 3D GIS content: utility lines, devices, 3D layers, basemap context, and the surrounding city environment.

This design keeps the GIS data management workflow familiar. GIS teams can prepare and update the web scene in the Esri environment, and the mobile app can consume that configured scene.

In practical terms, the app becomes a reusable AR viewer for the city's prepared 3D GIS mission.

3. Choosing an AR Mode

The user can choose between real-world AR and tabletop AR.

Real-world AR mode is designed for on-site viewing. It uses GPS and device orientation to position the scene relative to the physical environment. In this mode, users can see utility layers appearing in their camera view, with controls for heading and elevation adjustment.

Tabletop AR mode is designed for scaled review. The city scene appears as a compact model on a physical surface. Users can review a site, neighbourhood, or city-scale area, then discuss utility networks without being on-site.

This is valuable because not every coordination question happens in the field. Some happen in offices, council rooms, project meetings, or training sessions.

4. Adjusting Heading, Elevation, and Basemap Visibility

AR is only useful when the scene can be understood in context. The app includes controls for heading, elevation, and basemap visibility, allowing the user to tune the view.

Heading adjustments help orient the scene. Elevation controls help align the content vertically. Basemap opacity controls help the user decide how much map context should be visible behind or below the utility layers.

These controls may seem small, but they are central to AR usability. Field conditions are rarely perfect. Device sensors, GPS accuracy, indoor testing environments, and web scene elevation settings all influence how the AR scene appears.

5. Managing Layers

The app includes a layer panel that lets users toggle utility layers on and off. This is important because utility scenes can become visually dense.

Layers include:

    • Sewer_Main
    • Water_Main
    • Water_Devices
    • Sewer_Device
    • Open Channel
    • Sewer_Device_3D
    • Sewer_Main_3D
    • Water_Device_3D

Layer control turns the AR scene from a static visual into an operational viewer. A user can simplify the scene, focus on one utility network, or compare 2D and 3D representations.

6. Supporting Tabletop Focus and Scale

The tabletop mode includes focus options such as scene selection and device location, as well as scale options such as site, neighbourhood, and city extents.

This lets the user decide what kind of question they are answering. A site-scale view may support a specific project discussion. A neighbourhood-scale view may help identify network relationships. A city-scale view may support broader planning or executive review.

The Digital Advantage: How AR Helps Utility Coordination

Better Field Understanding

AR gives field users a way to see utility information in relation to their surroundings. This can help with orientation, coordination, and communication before work begins.

Again, AR should not be treated as a substitute for official utility locating or survey-grade positioning. Its strength lies in context: helping people understand what GIS identifies as nearby and how assets relate spatially.

Stronger Cross-Department Communication

Utility coordination often involves public works, GIS, engineering, planning, contractors, leadership, and sometimes the public. Each group may understand the same data differently.

A tabletop AR scene creates a shared visual reference. Instead of pointing to separate maps or reports, teams can gather around a single scaled 3D model and discuss the same utility network.

Reusable Mobile Architecture

Because the app is driven by a configured web scene, the same mobile pattern can support other cities, missions, and datasets. Once the web scene is ready, the app configuration can reference it and present it through the same AR experience.

This reduces the need for one-off applications and supports a more scalable digital twin strategy.

More Accessible 3D GIS

Not every stakeholder is comfortable navigating a full GIS application. AR can lower that barrier by making the scene more visual and direct. Users can tap, move, rotate, and inspect the scene in a way that feels closer to the physical world.

 

A Stronger End to the Digital Twin Workflow

 

 Series 1 and Series 2 focused on building richer 3D content. Series 3 asks the next question: how do people actually use that content when decisions are being made?

The answer is not one interface. It is a family of interfaces: web scenes for desktop review, apps for public engagement, and AR experiences for field and tabletop coordination.

 

This Is What We Learned

  • A good AR app starts with a good web scene. If layers, elevation, symbology, and 3D content are not prepared well, AR will quickly expose those issues.
  • Two AR modes are better than one. Real-world AR supports location-based viewing, while tabletop AR supports planning, meetings, and demonstrations.
  • Layer control is essential. Utility data can become visually crowded, so users need simple ways to turn layers on and off.
  • Calibration is part of the user experience. Heading, elevation, and basemap controls help users make the scene understandable in real conditions.
  • Authentication should match the mission. Demonstration scenes may allow anonymous access, while operational utility scenes may require secure sign-in.
  • The app should be configurable. The long-term value comes from changing the web scene, not rebuilding the app for every use case.

This Is What Not To Do

  • Do not treat AR as survey-grade locating. AR provides visual context, but official field verification and utility locating procedures still matter.
  • Do not overload the first AR view. Too many layers can make the scene confusing, especially on a phone screen.
  • Do not skip elevation preparation. Z-values, vertical alignment, and scene elevation settings directly affect user trust.
  • Do not ignore mobile performance. Heavy 3D layers, dense symbology, and large scenes should be optimised before field use.
  • Do not assume one view works for every user. Field crews, GIS analysts, engineers, and managers need different levels of detail.
  • Do not disconnect the app from the GIS workflow. The web scene should remain the source of truth for configured AR content.

You May Find Useful

  • ArcGIS Maps SDK for Swift - Augmented Reality scenes: Use Esri's Swift SDK to display global scenes in AR on iOS devices. link
  • ArcGIS Maps SDK for Kotlin - Augmented Reality scenes: Use Esri's Kotlin SDK to display scenes in AR on Android devices. link
  • ArcGIS Online Web Scenes: Configure and share 3D GIS scenes that can become the source content for mobile AR missions.
  • ArcGIS Pro 3D workflows: Prepare utility layers, elevation, symbology, and 3D content before publishing a scene.
  • Mobile device testing: Test GPS, heading, elevation, performance, and layer readability on the devices expected to be used in the field.

Closing Thought

Digital twins are often described as city-scale models. But their real value appears when people can use them in the moments when decisions are made.

Highland Park's first two stories showed how AI can help make buildings and transportation corridors more recognisable, contextual, and useful.

AR Mission shows the next step: integrating a 3D utility scene into a mobile experience to support field understanding, tabletop coordination, and everyday conversations.

That is the direction digital twins need to go.

Not just more data -  More usable data.

Not just better models -  Better decisions in the hands of the people doing the work.