Introduction
In this section, the development of plans and specifications is supported by providing the following information:
- Actors: who need to be considered in the development of the system.
- Architecture and Data flows: showing how administrators and users interact and use the system, to help identify and develop the needs and specifications of the system.
- Standards: that are important and how these are used in the context of this use case.
- Possible developments: in practices and technology that may provide opportunities in the future.
Actors
When developing an enhanced asset management process it is good practice to identify the actors who will interact with it, and ensure the system’s design and specification fulfil their needs. The functions of the system can then be described by its interactions with actors (any user or system that interacts with the system).
The following actors and needs have been identified as applicable for an asset management system:
Actor
|
Description
|
Needs
|
Road users
|
People who use road infrastructure and equipment |
Well maintained roads, Access to services providing information on assets and to report issues, Information on maintenance and renewal works (including streetworks) that can disrupt navigation and be a generator of delays |
Asset Manager
|
Role (within the authority) responsible for maintaining roads and the asset management system |
Functions that effectively support monitoring, management and reporting of road assets. |
Road maintenance contractors
|
Organisations that are contracted by authorities to maintain road infrastructure and equipment. |
Facilities to efficiently receive clear and accurate works instructions, identify defects and defect repairs, send status updates, and manage accounts. |
Statutory Undertakers
|
Companies and agencies with permission to undertake highway works. |
Long term works programmes for co-ordination of works, permits and road occupancy |
Road Inspector
|
People (typically within the authority, but maybe part of the maintenance contractor organisations) who assess the condition and defects of road infrastructure and equipment |
Facilities to efficiently receive accurate defect reports, plan their inspection routes, and capture and submit inspection records. |
Asset Management System Service Providers
|
Software developers and service providers deliver either software or maintained services to support Authority asset management processes |
Clarity of the functional needs to support asset management purposes, including the import, export, analysis, validation and reporting of assets and related data |
Data Suppliers
|
Typically commercial entities supply asset-related data emanating from various sources, for use by Asset Managers and Road Maintenance Contractors under a commercial arrangement |
Understanding of the needs, commercial constraints and delivery restrictions (such as acceptable data formats) for asset management use of data |
Architecture and Data Flows
The data requirements and data flows for asset management are tabulated in Figure 3 and Figure 4.
The idealised architecture and data flows are illustrated in Figure 5.
Interfaces
Interfaces between systems and services will depend on the specific design and the boundaries with other systems (regional, national, international) and services.
The general principle is that interfaces should be specified to use standardised data flows and protocols wherever standards are available. Following standards will support the integration of other systems and services.
Standards
There are limited recognised data standards for sharing asset register and condition data. However established guidance and codes of practice for asset management is available. As illustrated in Figure 1 the UK Roads Liaison Group (UKRLG) provides key asset management guidance for the highways sector in the UK. More information is available on the UKRLG website. Including the ‘Highway Infrastructure Asset Management Guidance Document’ which provides a framework of guidelines and recommendations for asset management and is further supported by several codes of practice published by UKRLG. This guidance is intended to assist Authorities in meeting their statutory asset maintenance obligations, for example, as set out in the Road Traffic Act 1980, and to manage transport assets effectively to maximise both benefits to road users and cost-effectiveness.
The Chartered Institute of Public Finance and Accountancy (CIPFA) has published a Code of Practice on Transport Infrastructure Assets. The code is intended to support consistent, high-quality financial information to support asset management, financial management and financial reporting. Conformance with this code is intended to ensure the satisfaction of Whole of Government Accounts (WGA) requirements for Authorities to report the value of their assets, including transport assets, using standard accounting practices. The CIPFA code requires the calculation of the Gross Replacement Cost and Depreciated Replacement Cost of highway assets. The trends of these metrics can be used as a basis for measuring the effectiveness of asset management and quantifying achievement against intended targets. For example, if the target is to maintain current condition levels, then the depreciated replacement cost should remain relatively level over time in real terms.
The CIHT’s ‘Well Managed Highway Liability Risk’ guidance document provides a risk and evidence-based approach to service delivery and the effective management of highway liability risk exposures. The use of connected data and digitalised processes in asset management can help to achieve this approach effectively and with consistency.
The Highway Maintenance Efficiency Programme (HMEP) recommends that long term strategic planning and estimation of expenditure, alongside long-term asset performance, is essential to improve the management of roads and services. They provide a Lifecycle Planning toolkit that calculates the likely performance of an asset so that future budgets can be prioritised accordingly. The Structures Asset Valuation and Investment Tool (SAVI) provides a similar condition-based decision support tool for structures. It can be used to: carry out the valuation of structures stock, develop prioritised short-term programmes of work, and develop long-term asset management plans. Integrating the functionality of these tools into the asset management system would improve efficiency by enabling these decision support forecasts to be provided automatically without additional effort being required to enter data into separate tools.
Figure 5: Idealised Asset Management System architecture

Possible Future Developments
Connected Vehicle Data Research published by DfT suggests that the use of emerging connected vehicle services could provide significant cost savings for asset management.
- Since the publication of the report, several new connected data services have come to market and usage of these is increasing across Authorities.
- Data types involved in these products include processed asset images from smartphone cameras, road surface condition data from accelerometers and crowdsourced defect reports as well as data from vehicles’ own sensors.
- These services will focus on the use of automatically collected data, combined with machine learning algorithms to augment or even replace typically labour-intensive surveys.
- A key advantage is identifying issues as they arise, rather than during scheduled inspections which allow:
- – A greater range of preventative and pre-emptive repairs of assets.
- – Reduction of labour costs due to earlier identification of problems.
- – Reduction of congestion due to more efficient repair and maintenance planning.
Services administered or authorised by an Authority such as refuse collection, or e-scooter rental could provide an ideal source of data for these future asset management services. In preparation for such future developments, Authorities could consider ensuring that the terms of new agreements facilitate the sharing and/or collection of data. Considering this for new agreements would have minimal cost implications, however, adapting existing agreements to facilitate access to data could be a significant barrier later.
On-going developments in technology are likely to continue to change the way that asset managers receive and access information and change the data sources available to Authorities for monitoring and understanding their assets on the network.
In particular, while conventional ITS systems include Authority controlled sub-systems (roadside equipment, traffic control centres), a central focus of current development is on the devices travellers carry with them or have in their vehicles – ‘smartphones’ and ‘sat navs’. These devices can communicate and share information and are anticipated to lead to improved road safety, traffic efficiency, comfort, mobility and sustainability.
The MfSS focuses on the services to be deployed by Authorities and the interfaces to these subsystems. Some of the functions of this use case will be similar regardless of the underlying technology to be deployed. Accordingly, the focus of an Authority should be on building and publishing accurate and complete data sets. When data is accurate, timely and complete, the developing ecosystem of service providers is more likely to use it to enhance their services, and provide publishing services to ensure that the Authority data is used more widely.
- As these developments will continue, Authorities should nevertheless:
- – Develop and make available high-quality data that is easy for service providers to find and use, so making it available to the publis.
- – Focus on service quality and service levels so data feeds can be relied upon and can be dependable.
- – Ensure published standards are used for interfaces wherever possible to maximise the potential for consumption of the published data.
- – Provide opportunities for service providers to trial new services to continue to learn and develop their capability to engage in this area.
- Assess whole life costs when considering investments in conventional ITS systems and investigate the use of other data sources (‘smartphones’, ‘sat navs’, video analytics) as contenders or complementary to traditional ITS solutions.
A relatively recent trend for inspection of high or hard to access structures is the use of unmanned aerial vehicles (UAVs) for inspection surveys. This eliminates risks of working at height, improves cost-effectiveness and potentially improves the quality and consistency of records. However, the use of UAVs presents a new set of risks and limitations. Over the coming years, available products and guidance will be required to optimise and regulate the safe use of UAVs in asset management.