ArcGIS provides the geospatial foundation, and iROADS operationalises that foundation for road asset management decision making.
For major highway and transport authorities, road asset management is no longer limited to storing network data or displaying assets on a map. The requirement is to convert trusted geospatial data into consistent and auditable maintenance decisions:
- Where is the network deteriorating considering cross-asset impacts?
- Which sections should be prioritised?
- What treatments are likely to deliver the best value?
- How should budgets be deployed to achieve the greatest long term impact?
This requires two capabilities that operate in a coordinated manner.
The first is enterprise geospatial infrastructure. This provides the organisation’s spatial backbone and the GIS environment used to manage the road network, asset locations, administrative boundaries, constraints, imagery, and reference layers. It is also where governance, security, version control, integration, and scalable analytics are implemented to provide a single, trusted view of the network across teams and functions.
The second is domain specific asset intelligence. A specialist road asset platform such as iROADS applies road sector logic to address operational and financial decision requirements:
- How will asset condition change over time considering specific asset models and cross-asset condition analysis?
- Which interventions should be prioritised for maintenance planning?
- What treatments are appropriate?
- How do different funding scenarios affect outcomes?
- Which interventions support better whole-life performance?
ArcGIS provides the enterprise geospatial foundation, and iROADS applies road asset analysis and decision support to that foundation.
This creates a clear opportunity for transport authorities to implement an integrated approach. The intent is not to select one platform in preference to the other, but to combine them in a way that is practical, open, and suitable for enterprise adoption.
Why does this matter now?
As infrastructure organisations prepare for more connected, standardised, and enterprise scale data environments, market expectations are changing. Programmes such as the Central Network Model indicate a wider shift toward stronger interoperability, improved data governance, and a greater expectation that specialist systems integrate effectively with the core geospatial estate.
This has become a business and operating model requirement as well as a technical requirement.
Authorities typically require an enterprise architecture that avoids additional data silos, duplicated network datasets, and disconnected workflows in which asset intelligence is managed outside the established GIS environment. In practice, they want specialist road asset capability that integrates with ArcGIS governance, security, and publishing patterns, strengthening the value of the existing platform while maintaining a single source of truth for the spatial estate. iROADS is designed to fulfil that requirement by consuming authoritative GIS layers and returning decision support outputs for use across the ArcGIS ecosystem.
Why ArcGIS is the spatial system of record for transport authorities
Esri’s ArcGIS platform is already established as the enterprise geospatial environment for many transport bodies and highway authorities. It provides the authoring, governance, sharing and analysis capabilities needed to manage complex networks at scale.
This is the layer where organisations maintain their authoritative road network, boundaries, basemaps, constraints and reference datasets. It is the place where GIS teams manage quality, publishing, access and control. It is also the environment through which maps, dashboards, web services and applications are delivered across the business.
Accordingly, ArcGIS functions as the spatial system of record and maintains the single source of truth for the spatial estate. This role should remain unchanged.
How iROADS adds road asset intelligence to ArcGIS
Where iROADS adds value is in the layer above that spatial foundation.
It brings the asset-specific logic needed to support better maintenance and investment planning. That includes deterioration modelling, scheme identification, treatment planning, budget scenario analysis, street works workflows and performance reporting.
This distinction is important. iROADS is not intended to replicate core GIS capabilities, since that would introduce an inappropriate architecture. Its role is to extend ArcGIS with specialised road asset intelligence.
This positioning typically aligns with authority requirements and enterprise architecture principles. It supports a model in which ArcGIS remains authoritative, governed, and central, while iROADS provides the road asset analytics required to support evidence based decision making.
Why road asset management needs integrated GIS and asset intelligence
The strongest integration model between ArcGIS and iROADS is based on open standards and clean separation of roles.
ArcGIS remains the single source of truth for the spatial estate. iROADS consumes the relevant network and contextual layers required for analysis and produces outputs that can be surfaced back into ArcGIS environments for mapping, dashboards, review, and operational action.
Under this model, road networks, administrative boundaries, and constraint layers flow from ArcGIS into iROADS as trusted context. In return, condition indicators, priority schemes, treatment recommendations, street works layers, and performance outputs flow back into ArcGIS for visualisation and operational use.
This is an effective integration pattern. It avoids unnecessary duplication of GIS master data and avoids forcing either platform beyond its intended role. It provides a practical model in which each component is responsible for the functions it is best suited to deliver.
How ArcGIS Dashboards, Experience Builder and ModelBuilder make iROADS outputs operational
The integration becomes suitable for enterprise adoption when iROADS outputs are operationalised through standard ArcGIS delivery patterns and repeatable workflows, not only published as layers.
ArcGIS Dashboards can present iROADS outputs as live operational views. When iROADS publishes condition, scheme and performance layers via OGC WFS and OGC API Features, these services can be consumed in ArcGIS web maps and surfaced in dashboards that combine maps with KPI and summary widgets. This supports network level monitoring, interactive drill down by area or hierarchy, and map linked charts that update based on feature selection. This allows programme teams and leaders to review where interventions are required, what treatments are proposed, and how budgets and outcomes vary, within the same governed ArcGIS view.
ArcGIS Experience Builder supports role based web applications for review and action. Dashboards are typically used for monitoring, whereas Experience Builder can package the same maps and services into controlled workflows, such as a scheme review application that combines iROADS prioritised schemes with authoritative constraint layers, or a planning application that enables teams to filter and compare candidate interventions and scenarios across ArcGIS Enterprise or ArcGIS Online.
For GIS teams, ArcGIS Pro 3.6 remains the environment for high assurance authoring and repeatable processing. ModelBuilder can be used to automate and audit common integration steps, such as validating schemas and geometry, preparing standardised context layers, producing consistent derived layers for publication, and packaging updates into governed services in ArcGIS Enterprise, ArcGIS Server, or ArcGIS Online. This reduces manual effort and improves integration reliability over time.
Why road asset management buyers value ArcGIS and iROADS integration
Integration protects existing GIS investment. Many authorities have implemented ArcGIS as an enterprise platform with defined governance, data management processes, role based access controls, and established workflows for publishing and consuming spatial services. Specialist road asset tooling is therefore expected to align with that operating model and extend it, rather than introduce a competing repository or parallel delivery stack.
Integration also supports operational alignment between GIS and asset management functions. GIS teams can continue to steward the authoritative spatial datasets as a single source of truth, while asset management teams use iROADS to apply road asset logic, undertake deterioration and scenario analysis, and generate prioritised interventions for maintenance planning. This division of responsibilities reduces duplication, clarifies ownership, and improves traceability from published data to decision outputs.
Finally, it provides architectural flexibility over time. Standards based integration patterns can be governed more consistently, scaled across business units, and evolved as data models, reporting obligations, and platform capabilities change. This approach reduces vendor lock in at the interface level and supports incremental modernisation without destabilising the core geospatial estate.
Turning geospatial data into better road maintenance decisions
This distinction has practical implications for how authorities design their data and decision making architecture.
A GIS platform describes asset location, spatial relationships, and the controls required to govern that information across the organisation. A road asset management platform such as iROADS interprets condition and performance, models future deterioration, and supports selection of appropriate interventions.
This distinguishes geospatial visibility from asset decision intelligence, and authorities typically require both.
Without strong geospatial infrastructure, asset decisions are not grounded in trusted network context. Without specialist road asset intelligence, even a mature GIS environment does not answer the practical intervention questions that decision makers need to resolve.
In combination, these capabilities enable organisations to move from authoritative spatial data to defensible, network wide maintenance decisions.
Why the Road Asset Management Market Needs ArcGIS and iROADS
The intended position is straightforward. iROADS integrates with Esri ArcGIS because this reflects an appropriate enterprise architecture for modern road asset management.
ArcGIS provides the enterprise geospatial foundation, and iROADS adds the road asset intelligence layer. Together, they support an integrated, scalable approach to network management that is suitable for long term planning and investment decision making.
This is an integration approach, not a replacement of ArcGIS, and not an overlapping or standalone add on capability. ArcGIS remains the enterprise geospatial platform, while iROADS provides specialist road asset decision support that operates against the authoritative spatial context.
This standards-based integration approach helps authorities realise greater value from the ArcGIS environment they already rely on, while adding the specialist intelligence required to improve road asset decisions.
The future of road asset management will favour organisations that can connect trusted geospatial infrastructure with specialist decision support capability.
ArcGIS provides the geospatial foundation, and iROADS makes that foundation operational for road asset management decision making.
For authorities facing increasing pressure to improve network performance, justify investment, and align with broader digital and data programmes, this combination provides a clear and practical basis for delivery.
