DELIVERABLE NO: D3.1 DISSEMINATION LEVEL: PUBLIC TITLE ... · deliverable report deliverable no:...
Transcript of DELIVERABLE NO: D3.1 DISSEMINATION LEVEL: PUBLIC TITLE ... · deliverable report deliverable no:...
Grant Agreement Number: 713793
Project Type: H2020-MG-8.4b-2015-smart governance, network resilience and streamlined delivery of
infrastructure innovation
Project acronym: AM4INFRA
Project title: common framework for a european life cycle based asset management approach for
transport infrastructure networks
Project start date: 01/09/2016
Project website: www.am4infra.eu
Technical coordination Rijkswaterstaat (NL) (www.rijkswaterstaat.nl)
Project management Uniresearch (NL) (www.uniresearch.nl)
DELIVERABLE REPORT
DELIVERABLE NO: D3.1
DISSEMINATION LEVEL: PUBLIC
TITLE: ASSET DATA DICTIONARY
DATE: 29/03/2018
VERSION: FINAL
AUTHOR(S): ELISABETTA MARCOVALDI (ANAS), MAURIZIO BICCELLARI (ANAS)
REVIEWED BY: PETER SCOTT (HE), ALAN DUNFORD (HE), RAMESH SINHAL (HE)
APPROVED BY: TECHNICAL COORDINATOR – RUUD SMIT (RWS)
H2020-MG-2015-713793— common framework for a European life cycle based asset management approach for transport
infrastructure networks
Acknowledgement:
The author(s) would like to thank the partners in the project for their valuable comments on previous drafts and for
performing the review.
Project partners:
1 - RWS – MINISTERIE VAN INFRASTRUCTUUR EN MILIEU – NL
2 - HE – HIGHWAYS ENGLAND COMPANY LTD – UK
3 - ANAS – ANAS SPA – IT
4 - FEHRL – FORUM DES LABORATOIRES NATIONAUX EUROPEENS DE RECHERCHE ROUTIERE – FR
5 - TII – NATIONAL ROADS AUTHORITY – IE
6 - UNR – UNIRESEARCH BV – NL
7 - CERTH – ETHNIKO KENTRO EREVNAS KAI TECHNOLOGIKIS ANAPTYXIS- GR
8 - WI – WUPPERTAL INSTITUT FUR KLIMA, UMWELT, ENERGIE GMBH - DE
Disclaimer:
This project has received funding from the European Union’s Horizon 2020 research and innovation
programme under Grant Agreement no. 713793. This document reflects the views of the author(s)
and does not necessarily reflect the views or policy of the European Commission. Whilst efforts
have been made to ensure the accuracy and completeness of this document, the AM4INFRA
consortium shall not be liable for any errors or omissions, however caused.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 3 / 82
Contents
Contents .............................................................................................................................................................................. 3
Executive Summary .................................................................................................................................................... 5
1 Purpose of the document ...................................................................................................................................... 6
1.1 Document structure ............................................................................................................................................ 6
1.2 Deviations from original Description in the grant agreement annex 1 part a ..................................................... 6
1.2.1 description of work related to deliverable in GA annex 1 – part a...................................................................... 6
1.2.2 time deviations from original planning in ga annex 1 – part a ............................................................................ 6
1.2.3 content deviations from original planning in GA annex 1 – part a ...................................................................... 6
2 Introduction .......................................................................................................................................................... 7
2.1 Integration with AM4INFRA Framework Architecture ........................................................................................ 7
3 Adopted Methodology .......................................................................................................................................... 8
3.1 Step 1 - Asset Data Management Assessment .................................................................................................... 8
3.1.1 Survey on asset data management ..................................................................................................................... 9
3.1.2 Comparison on asset data management practices ............................................................................................. 9
3.2 Step 2 - Asset Data Dictionary Delivery ............................................................................................................. 10
4 Asset Data Objectives .......................................................................................................................................... 11
5 Asset Core Data Model ........................................................................................................................................ 12
6 Asset Data Life Cycle ............................................................................................................................................ 13
7 Asset Data Dictionary Contents ........................................................................................................................... 14
7.1 Network Location Referencing Data Group....................................................................................................... 16
7.2 Asset Inventory Data Group .............................................................................................................................. 17
7.3 Construction Data Group ................................................................................................................................... 22
7.4 Condition & Performance Data Group .............................................................................................................. 23
7.5 Risk & Safety Data Group .................................................................................................................................. 26
7.6 Maintenance Data Group .................................................................................................................................. 26
7.7 Financial & Accounting Data Group................................................................................................................... 27
7.8 Operational Data Group .................................................................................................................................... 28
8 Conclusion ........................................................................................................................................................... 30
9 References ........................................................................................................................................................... 31
Annex I – Asset Inventory Datasets ........................................................................................................................... 32
Annex II – Asset Data Dictionary ............................................................................................................................... 55
Annex III - Survey on Asset Data Management Practices .......................................................................................... 56
SURVEY REPLY BY HIGHWAYS ENGLAND ..................................................................................................................... 62
SURVEY REPLY BY TRANSPORT INFRASTRUCTURE OF IRELAND .................................................................................. 69
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 4 / 82
SURVEY REPLY BY ANAS ............................................................................................................................................... 77
Figures Figure 0-1 Asset Core Data Scheme ............................................................................................................................................... 5
Figure 1-1. Asset Common Data Management Approach .............................................................................................................. 7
Figure 2-1. Asset Data Dictionary Design – Adopted Methodology ............................................................................................... 8
Figure 2-2. Approach for Asset Data Management Assessment .................................................................................................... 9
Figure 2-3. ADD extract ................................................................................................................................................................ 10
Figure 4-1. Asset Core Data Scheme ............................................................................................................................................ 12
Figure 5-1. Asset Data Phases ...................................................................................................................................................... 13
Figure 6-2. Network Topology model ........................................................................................................................................... 16
Figure 6-3. ADD Level of Depth .................................................................................................................................................... 18
Figure 6-4. Categories for “Asset Inventory” Data Group ............................................................................................................ 18
Tables Table 6-1 Metadata for ADD data items ...................................................................................................................................... 14
Table 6-2 Datasets category ......................................................................................................................................................... 14
Table 6-2 Network Dataset .......................................................................................................................................................... 16
Table 6-3 Corridor Dataset ........................................................................................................................................................... 16
Table 6-4 Node Dataset ................................................................................................................................................................ 17
Table 6-5 Link Dataset .................................................................................................................................................................. 17
Table 6-6 Link Section Dataset ..................................................................................................................................................... 17
Table 6-7 Asset Inventory Datasets .............................................................................................................................................. 18
Table 6-8 Asset Construction Dataset .......................................................................................................................................... 22
Table 6-9 Asset Installation Dataset ............................................................................................................................................. 23
Table 6-10 Asset Lifecycle Dataset ............................................................................................................................................... 23
Table 6-11 Asset Performance Dataset ........................................................................................................................................ 24
Table 6-12 Asset Condition Dataset ............................................................................................................................................. 24
Table 6-13 Asset Inspection Dataset ............................................................................................................................................ 25
Table 6-14 Asset Risk Dataset ...................................................................................................................................................... 26
Table 6-15 Asset Defect Dataset .................................................................................................................................................. 26
Table 6-16 Maintenance Work Dataset ....................................................................................................................................... 27
Table 6-17 Asset Valuation Dataset ............................................................................................................................................. 27
Table 6-18 Asset Expenditures Dataset ........................................................................................................................................ 28
Table 6-19 Asset Funds Dataset .................................................................................................................................................. 28
Table 6-20 Asset Access Restriction Dataset ................................................................................................................................ 28
Table 6-21 Asset Event Dataset .................................................................................................................................................... 29
Table 9-1 Asset Inventory Datasets .............................................................................................................................................. 32
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 5 / 82
Executive Summary
Effective and efficient Asset Management by infrastructure owners and operators needs to be based on a solid, valid and
complete set of asset data and information. The key objectives demanded to asset data are several like to describe the asset
and its performance, to provide the basis for informed decision making, to facilitate communications with stakeholders, etc.
Main challenge is therefore to guarantee an effective asset data management building a Common Data Environment (CDE)
that, also according to PAS 1192 standard, allows having, for any given asset, a unique source of information to disseminate
all relevant asset information to several stakeholders in a managed process.
To support improvement of asset data management across transportation network stakeholders (owners, managers and
operators) AM4INFRA Work Package 3 “Data and Information Management” has identified the design of an Asset Data
Dictionary as first pillar of an asset data common approach. An Asset Data Dictionary (ADD) identifies which are the relevant
information and related attributes that can constitute a common data dictionary for asset data management.
The methodological approach adopted by WP3 has been to begin with a preliminary analysis on asset data management with
the aim of collecting relevant findings and best practices; for this scope a specific survey has been arranged and disseminate
to AM4INFRA partners. Then from the findings emerging by the assessment, ADD has been designed and drawn up. In terms
of level of depth for the ADD, a balance between information needs from asset stakeholders and actual asset data managed
by NIAs IT systems has been performed. The ADD developed by WP3 has the following hierarchical structure:
Data Group (“Domain”): a logical grouping of data associated to a specific asset management field/knowledge (e.g.
maintenance process, road infrastructure, etc.)
Dataset: data set corresponds to the contents of a single table where each row corresponds to a given data item of
the data set in question;
Data Item: basic element, with its own description, corresponding to the lowest object of asset dictionary;
Regarding ADD contents, they can be summarized as follows:
Two core data groups (Network Location Referencing, Asset Inventory) to identify both the network topological
model and the asset register; within asset register, asset types should be characterized according to the network
type (e.g. road, rail or waterway);
Six data groups, which information could be common across transportation assets (Construction, Condition &
Performance, Risk & Safety, Maintenance, Financial & Accounting, Operational);
Figure 0-1 Asset Core Data Scheme
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 6 / 82
1 Purpose of the document
1.1 DOCUMENT STRUCTURE
The contents of the document are organized according to the following structure:
A brief description of the work done during the task in order to identify the Asset Data Dictionary (ref.
“Introduction”and “Adopted Methodology Sections”)
An overview of asset data management core principles emerged during the task (ref. “Asset Data Objectives”, “Asset
Core Data Model” and “Asset Data Life Cycle” Sections)
Presentation of the Asset Data Dictionary contents (ref. “Asset Data Dictionary contents” Section)
1.2 DEVIATIONS FROM ORIGINAL DESCRIPTION IN THE GRANT AGREEMENT ANNEX 1 PART A
1.2.1 DESCRIPTION OF WORK RELATED TO DELIVERABLE IN GA ANNEX 1 – PART A
The task aims at understanding and formalizing which are the relevant information and related attributes that can constitute
a common data dictionary for asset data management. To achieve this goal, during the task, best practices and key evidences
emerging from available reports and studies related to asset data management will be taken into account. A comparison
between the previous analysis with definitions, naming conventions and values used by different NIAs will also be performed.
Furthermore, a federated database model will be designed in order to create useful information by combining, integrating,
and linking data from the various sources. Included in the activities, a systematic approach to the development of asset
information registers will be developed.
1.2.2 TIME DEVIATIONS FROM ORIGINAL PLANNING IN GA ANNEX 1 – PART A
No time deviations have occurred during the task.
1.2.3 CONTENT DEVIATIONS FROM ORIGINAL PLANNING IN GA ANNEX 1 – PART A
No content deviations have occurred during the task.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 7 / 82
2 Introduction
An effective and efficient Asset Management by infrastructure owners and operators needs to be based on a solid, valid and
complete set of asset data and information. The data coming from the several corporate systems related to asset management
need to be integrated, combined and elaborated to provide consistent information to decision making processes. This issue
can no longer restricted to a single country road network, but it needs to be faced at European level to guarantee a common
approach for asset information management and ensure uniform standards on TEN-T network.
Common data and data management means that the stakeholders (owners, managers and service providers) in the Member
States identify, agree and learn to use meaningful standards for cross-European information management (which data, how to
use it, and how to translate it into the required information). And, that they identify, agree and become acquainted with
adequate frameworks (data management systems) for a European information management model that enables asset owners,
asset managers, and service providers to effectively and efficiently carry out their tasks; interoperable across modes and
borders.
Figure 2-1. Asset Common Data Management Approach
As first step of this approach, the task of Asset Data Dictionary Design aimed at understanding and formalizing which are the
relevant information and related attributes that can constitute a common data dictionary for asset data management. To
achieve this goal, during the task, best practices and key evidences emerging from available reports and studies related to asset
data management has been taken into account.
2.1 INTEGRATION WITH AM4INFRA FRAMEWORK ARCHITECTURE
The framework architecture defined in WP1, and detailed in
D1.1, is based on core elements, where concepts like use and
share of common data have to be taken into account in all
steps of network management, network enhancement and
network expansion.
The Asset Data Dictionary is therefore an artefact that
concretely supports the Framework, as a common data needs
a common dictionary in order to perform an effectively
sharing of information.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 8 / 82
3 Adopted Methodology
To build the Asset Data Dictionary, the methodology adopted for the task, as shown in the following figure, has been the
following:
Step 1 – Asset Data Management Assessment: preliminary analysis with the aim of collecting relevant findings and
best practices regarding asset data management in the transportation network, as inputs to design the Asset Data
Dictionary;
Step 2 – Asset Data Dictionary Delivery: starting from findings from step 1 design and draw up of the asset data
dictionary, in terms of data groups, datasets and data items;
Figure 3-1. Asset Data Dictionary Design – Adopted Methodology
3.1 STEP 1 - ASSET DATA MANAGEMENT ASSESSMENT
For Step 1, a dual approach (top down and bottom up) has been implemented in order to achieve the following goals:
definition of data sources and datasets as basis to design an asset data dictionary;
identification of Asset Management Best Practices related to Data Management;
The activities carried out during Step 1 are the following:
Drawing up of a survey on Asset Data Management Practices in order to collect information on how the organizations,
with responsibility on a transportation infrastructure network, manage information and data related to assets through
IT systems;
Analysis of the survey's replies received from AM4infra WP3 Partners;
Scouting and collection of relevant public reports and standards (e.g. PAS 1192, PAS 55, EraNET, Code of Practice on
Transport Infrastructure Assets, etc.) regarding Asset data management in the transportation sector;
Collection of relevant documents (policy, procedures, etc.) regarding asset data management practices within WP3
Partners;
Identification of common standards among organizations regarding asset data classification, data sources adopted,
and datasets stored in IT systems for asset management purposes
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 9 / 82
Figure 3-2. Approach for Asset Data Management Assessment
3.1.1 SURVEY ON ASSET DATA MANAGEMENT
The survey aimed at investigating how the organizations, with responsibility on a transportation infrastructure network,
manage information and data related to assets through IT systems. The areas of the survey (see Annex III - Survey on Asset
Data Management Practices) are organised as follows:
General context: general elements in order to characterize the organization in terms of:
transportation infrastructure managed network
Asset Management adopted framework
Asset Data Management: relevant elements related to asset data management model adopted by the organization
along the following core areas:
Asset Information Model in order to:
Deepen which information are tracked in the organization's asset management IT systems,
representing the key asset data sources;
Verify the implementation of a Corporate Asset Data Model, meant as a Common Data
Environment (CDE) that allows to have a single source of information for any given asset, used to
collect, manage and disseminate all relevant approved files, documents, and data for multi-
disciplinary teams in a managed process
Asset Data Management Processes in order to investigate how the organization performs the
collection, the update, the storing and exchange of asset data;
Asset Data Classification in order to gather a preliminary set of core datasets, adopted by organization
to manage infrastructure assets through several information domain.
From the replies received by AM4INFRA partners and discussions during General Assembly meetings, the following key findings
emerged:
IT systems cover mostly all key asset information domains (Financial, Technical, Managerial, etc.), however the
implementation of common data Environment (CDE), according to PAS 1192 standard, is at an initial level;
There isn’t any specific practice in Master Data Management;
Only one agency (Highways England) has adopted an Asset Data Dictionary within the organization;
Regarding asset data classification, there is a general convergence on common elements related to transportation
infrastructure like structure, lighting, equipment, etc.;
3.1.2 COMPARISON ON ASSET DATA MANAGEMENT PRACTICES
In order to define the structure and the contents of the ADD, a comparison among the survey outcomes, practices within NIAs
and the ones derived from collected reports has been performed.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 10 / 82
The key findings related to this analysis are:
Asset Data are always recorded and stored according to a specific hierarchy; as mentioned in Highway Infrastructure
Asset Management - Guidance Document (see References), there may be advantages in classifying assets in consistent
groups, for example the Code of Practice on Transport Infrastructure Assets adopts a three layer approach for
selecting and grouping assets.
Level 1 Level 2 Level 3
Asset Type Asset group Asset Item or Components
that level 2 implicitly covers
The asset data items are grouped in accordance with standard asset management functional practice and the data
items are presented to suit data architecture requirements; the groups’ number and naming varies among NIAs but
some common elements can be found in each data dictionary (e.g. Network, Inventory, Condition);
Regarding classification of assets within an inventory category, some differences can be found; for example the asset
“Tunnel” in some cases (e.g. Highways England) is considered a distinct asset type, whereas in others practices (e.g.
ANAS) Tunnel is considered within the Asset Type “Structure”;
3.2 STEP 2 - ASSET DATA DICTIONARY DELIVERY
Starting from the key findings emerging from Step 1, as common practices, terms for asset data management (e.g. standard
datasets, attributes and relations between datasets) the delivery of the asset data dictionary (ADD) has been carried out
through:
Asset Core Data Scheme definition: identification of data groups/domains, design of links between datasets,
association of datasets to data groups
ADD Contents’ completion: list of items associated to datasets and related attributes, ADD drawing up and delivery
Figure 3-3. ADD extract
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 11 / 82
4 Asset Data Objectives
The adoption of an effective asset management approach in a cross-European scenario needs the availability of reliable asset
data that support all the asset management processes and that can be shared with the stakeholders (owners, managers and
service providers) in the Member States.
The key objectives demanded to asset data can be summarized as follows:
To provide the data required to support the approach to asset management;
To describe the asset and its performance;
To provide the basis for informed decision making;
To facilitate communications with stakeholders;
To inform the assessment and management of risk;
To support the management of statutory requirements;
To support continuous improvement.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 12 / 82
5 Asset Core Data Model
A Common Data Environment (CDE), according to PAS 1192 standard, allows having a unique source of information for any
given asset, used to collect, manage and disseminate all relevant approved files, documents, and data for multi-disciplinary
teams in a managed process.
An Asset Core Data Model represent the first step to build a CDE shared among asset stakeholders; the following pillars have
been identified to perform the management of the assets constituting a transportation network (i.e. Road, Rail, etc.), through
their lifecycle (i.e. Planning, Design, Construction, Maintenance, Disposal):
Data related to Transportation Network Boundary in terms of adopted Topology and Location Referencing System;
Data related to the assets present along Transportation Network organized in hierarchies and categories as follows:
Inventory Data group: data to describe the asset is terms of what it is, where it is, what it does.
Construction Data group: data that is captured at the completion of the process of bringing an asset
functioning within the transportation network (e.g. delivery dates, commissioning data, etc.)
Condition & Performance Data group: data to describe the state of an asset at a particular instance in time
and how the asset is performing;
Risk & Safety Data group: data directly related to risk and safety topics associated with the infrastructure
assets (e.g. risk assessments, defects, inspections, etc.).
Maintenance Data group: data to describe information regarding asset maintenance processes;
Financial & Accounting Data group: data to describe costs and investments occurring on the assets
Operational Dataset: data to describe events occurring on the assets (e.g. temporary restrictions, accidents,
etc.)
The above categories are dependent one from another, as data may be considered to exist in more than one data category
(e.g. a defect might be considered as an illustration of the assets condition, or it might indicate an aspect of the performance
of the asset and when remedied, could be maintenance data).
Figure 5-1. Asset Core Data Scheme
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 13 / 82
6 Asset Data Life Cycle
Data for asset management are dynamically collected and created in phases that correspond to the general lifecycle of asset
data:
Data Creation: this phase refers to the development of the asset inventory. For transportation assets, inventory data
is typically created by either translating the as-constructed documentation or by field identification and measure of
the existing assets;
Data Collection & Updating: this phase refers to the data required for asset management planning purposes. This
data is collected following asset acquisition (operations and maintenance phase) and provides the base data for
analysis of asset condition, utilisation, and performance;
Data Analysis: this phase aims at performing analysis on the raw data with the purpose of drawing conclusions;
Data Maintenance: this phase refers to the ongoing storage, updating, and reporting of data and applies to all phases.
Figure 6-1. Asset Data Phases
Asset data on a transportation network can basically have three distinct states depending upon the data type:
Static data that does not change over time (e.g. pavement construction data);
Dynamic data that changes over time, however periodically (e.g. expenditures occurring over an asset);
Real-time data measured on a continuous basis and changing dynamically (e.g. traffic flow, weather data, etc.)
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 14 / 82
7 Asset Data Dictionary Contents
According to the Asset Core Data Model, the Asset Data Dictionary (ADD) represents a collection of relevant information linked
to the assets and asset management processes.
The asset data dictionary has the following hierarchical structure:
Data Group (“Domain”): a logical grouping of data associated to a specific asset management field/knowledge (e.g.
maintenance process, transportation infrastructure, etc.)
Dataset: data set corresponds to the contents of a single table where each row corresponds to a given data item of
the data set in question;
Data Item: basic element, with its own description, corresponding to the lowest object of asset dictionary;
Each Dataset included in the ADD has a defined set of data items, where each attribute is defined by the metadata elements
shown in the table below:
Table 7-1 Metadata for ADD data items
In the ADD for Data type the following categories have been considered:
A = Alphabetical;
AN = Alphanumeric
I = Integer;
DC = decimal;
D = Date;
B = Boolean
Regarding the datasets, it is possible to identify two different categories:
Multimodal dataset: dataset representing information that can be associated to various transportation mode (e.g.
maintenance dataset, financial dataset, etc.)
Specific modal dataset: dataset representing information typically referring to a specific transportation mode (e.g.
road, rail, etc.)
The following table enlist all the datasets included in the ADD and related category:
Table 7-2 Datasets category
Datagroup Dataset name Category
Multimodal Road mode Rail mode
Network Location Referencing Network x - -
Corridor x - -
Node x - -
Link x - -
Link Section x - -
Asset Inventory - Carriageway Pavement - x -
Road Markings - x -
Road Stud - x -
Kerb - x -
Shoulder (Carriageway) - x -
Foot/cycleway - x -
Asset Inventory - Track Rail - - x
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 15 / 82
Datagroup Dataset name Category
Multimodal Road mode Rail mode
Fastening - - x
Sleeper - - x
Ballast - - x
Switch blades - - x
Point Machine - - x
Shoulder (Railway) - - x
Asset Inventory - Earthworks Embankments x - -
Cutting x - -
At-Grade x - -
Asset Inventory - Structure Bridge x - -
Retaining Wall x - -
Tunnel x - -
Asset Inventory - Drainage Culvert - x -
Ditch - x -
Manhole - x -
Catch pits - x -
Outfall - x -
Filter Drain - x -
Asset Inventory - Lighting Lighting Column x - -
Lighting Unit x - -
Asset Inventory - Furniture Barrier - x -
Billboard - x -
Fence x - -
Gate x - -
Level Crossing - x -
Marker Post - x -
Pole x - -
Sign x - -
Sign Gantry x - -
Vegetation (Tree /Hedge) x - -
Asset Inventory - Equipment SOS Pillar - x -
Traffic Camera - x -
Traffic Signal x - -
VMS - x -
Weather Station x - -
Controller Cabinet x - -
ITS Asset x - -
Asset Inventory - Electrification
system
Overhead line - - x
Third rail - - x
Transformer - - x
Construction Asset Construction x - -
Asset Installation x - -
Condition & Performance Asset Condition x - -
Asset Inspection x - -
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 16 / 82
Datagroup Dataset name Category
Multimodal Road mode Rail mode
Asset Lifecycle x - -
Asset Performance x - -
Risk & Safety Asset Defect x - -
Asset Risk x - -
Maintenance Maintenance Work x - -
Financial & Accounting Asset Expenditures x - -
Asset Funding x - -
Asset Valuation x - -
Operational Asset Access Restriction - x -
Asset Event x - -
7.1 NETWORK LOCATION REFERENCING DATA GROUP
This data group provides the datasets and data items that describe the elements to create network location references that
help to trace the presence of the assets along the network (especially if a geo referencing system is not in place). Datasets
included in this Data Group are the following:
Network: general data related to the transportation network;
Corridor: logical items that constitute the transportation network, it can be a roadway, a railway or a waterway;
Node: Intersection points of links within a transportation network.
Link: logical portion of a road/rail (single links) between two junctions or interchanges or intersections.
Link section: a link can further subdivided in section; a section of a road has typically homogenous features such as
traffic and loading volumes, pavement type, width, number of lanes, etc.
Figure 7-1. Network Topology model
Table 7-3 Network Dataset
Code Name Description Data Type
0.1.1 Name Name of the transportation network A
0.1.2 Type Network Type (Rail, Road, Waterway) A
Table 7-4 Corridor Dataset
Code Name Description Data Type
0.2.1 Corridor ID Unique reference identifier for an existing Corridor AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 17 / 82
Code Name Description Data Type
0.2.2 Corridor name Corridor name spelled in full A
0.2.3 Corridor type Type of Corridor (Roadway, Railway, Waterway) A
0.2.4 Length Corridor total length in km DC
Table 7-5 Node Dataset
Code Name Description Data Type
0.3.1 Node Id Unique reference identifier for the network node AN
0.3.2 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the node on the
transportation network DC
Table 7-6 Link Dataset
Code Name Description Data Type
0.4.1 Link ID Unique reference identifier for the network link between two
nodes. AN
0.4.2 Link traffic flow
The flow direction of traffic on the link. This can either be one or
two way flow. One way flow can be in the increasing or
decreasing direction. The increasing direction is denoted by the
direction of travel from the start node to the end node
A
0.4.3 Link length The actual distance between the start and end node for a road.
This is the link length DC
0.4.4 Start Node Id Unique reference identifier for the link starting node AN
0.4.5 End Node Id Unique reference identifier for the link ending node AN
Table 7-7 Link Section Dataset
Code Name Description Data Type
0.5.1 Link Section Id A link that is broken into more than one part creates a link
section. Each link section has a unique ID to identify it. AN
0.5.2 X,Y,Z coordinate start
link section
The X,Y,Z coordinate locator point that defines the start link
section on the transportation network DC
0.5.3 X,Y,Z coordinate end link
section
The X,Y,Z coordinate locator point that defines the end link
section on the transportation network DC
0.5.4 Link ID Define the link whose the section belongs AN
7.2 ASSET INVENTORY DATA GROUP
This data group aims at identifying and describing network transportation key assets in terms of types, location, size, technical
aspects, etc. Therefore, these data are the core inventory from which an organization can base its asset management
processes.
For the classification and grouping of the assets types, level of depth has been setup on best practices arise during the task,
balancing information needs from stakeholders and actual data managed by NIAs, in order to design a model that can be
diffusely applied.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 18 / 82
Figure 7-2. ADD Level of Depth
Within Asset inventory Data Group, the following asset categories, representing only a logical grouping, has been identified:
Figure 7-3. Categories for “Asset Inventory” Data Group
Within each asset category, datasets, whose full contents are presented in the Annex I – Asset Inventory Datasets, are the
following:
Table 7-8 Asset Inventory Datasets
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 19 / 82
Asset Category Asset Type/Dataset Asset Type Description
1. Carriageway
1. Pavement
The portion of a road placed above the design subgrade
level for the support of vehicular traffic, and upon which the
pavement surface (wearing course) is applied
2. Road Marking
Lines, painted or otherwise applied, that delineate lane
boundaries and guide traffic with respect to overtaking and
the like.
3. Road Stud
Colourised, lit or reflective, studs placed on or into the
carriageway to assist the user with lane guidance and
delineation
4. Kerb A border, usually upstanding at the edge of carriageways,
hard shoulders and around central islands/traffic islands.
5. Shoulder (Carriageway) Part of the roadway between the carriageway and the ditch
or the (cutting or embankment) slope
6. Foot/cycleway Road part, next to the carriageway, reserved to pedestrians
or bicycles.
2. Track
1. Rail Bar of steel forming a track for locomotives
2. Fastening Metal elements that keep together the rails with the
sleepers
3. Sleeper Transverse beam that provides vertical and lateral support
to rail and fastening
4. Ballast
Single sized granular material of specified properties, placed
on the blanket, subgrade or structure to provide vertical and
lateral support to the sleepers
5. Switch Blades Mechanical installation the enable railway trains to be
guided from one track to another
6. Point Machine Device for operating railway turnouts
7. Shoulder (Railway) Part of the railway between the track and the ditch or the
(cutting or embankment) slope
3. Earthworks
1. Embankments Earthwork that extends below the road/railway formation
2. Cutting Earthwork that extends above the road/railway formation
3. At-Grade Earthwork that may be level with, extend above, or extend
below the road/rail formation
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 20 / 82
Asset Category Asset Type/Dataset Asset Type Description
4. Structure
1. Bridge A structure designed to provide passage for road users over
an obstacle by spanning it.
2. Retaining Wall A wall constructed to resist lateral pressure from the
adjoining ground or to maintain in position a mass of earth
3. Tunnel
A tunnel is an underground way, dug through the
surrounding soil and enclosed except for the entrance and
exit
5. Drainage
1. Culvert
One or more adjacent pipes or enclosed channel that
conveys surface water run-off, or a stream, below the
formation level of a road/rail
2. Ditch A long narrow trench or furrow dug in the ground, as for
drainage
3. Manhole A shaft with a removable cover that leads down to a sewer
or drain
4. Catch pit
A pit in a drainage system in which matter that might
otherwise block a sewer is collected so that it may
periodically be removed
5. Outfall Discharge point of a waste stream into a body of water
6. Filter Drain
A filter drain is a trench lined with a geotextile and filled with
gravel into which runoff water is led, either directly from the
drained surface or via a pipe system.
6. Lighting
1. Lighting Column A lighting installation usually consisting of a column, lantern
housing and lamp.
2. Lighting Unit A lighting unit that could be installed along the network (e.g.
inside tunnels)
7. Furniture
1. Barrier
A structure that provides protection from errant vehicles/
road users for safety or other purposes (e.g. noise
reduction)
2. Billboard A large outdoor advertising structur, typically found in high-
traffic areas such as alongside busy roads
3. Fence
A permanent structure that encloses an area, often
constructed with posts connected by rails. It can be provided
for protection for an area, security or to define a boundary.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 21 / 82
Asset Category Asset Type/Dataset Asset Type Description
4. Gate A gate in a fence, wall or barrier which allows access across
the fence, wall or barrier.
5. Level Crossing Intersection where a railway line crosses a road or path at
the same level
6. Marker Post Post erected alongside the carriageway to give warning or
guidance
7. Pole A structure onto which other assets could be connected
such as traffic signal, street lights, CCTV cameras.
8. Sign
Typically traffic signs that can be a board, plate, screen or
other device displaying words, figures, symbols or anything
else to regulate, direct, or warn users.
9. Sign Gantry
Fixed structure comprising one or two columns linked at
their tops by a beam spanned across the carriageway and
permitting the installation of traffic signs/equipments above
the lanes
10. Vegetation
(Tree /Hedge)
Distinct linear planting strips. They can be with or without
trees, and within the road corridor (usually marking
boundary lines or central reserves) which are intended to be
formally shaped and maintained.
8. Equipment
1. SOS Pillar Device installed along the roadway that allow users to
communicate in case of emergency
2. Traffic Camera Video camera system to observes vehicular traffic on a road
3. Traffic Signal
Signaling devices positioned at road intersections,
pedestrian crossings, and other locations to control flows of
traffic
4. VMS Sign capable of displaying predefined or freely
programmable messages
5. Weather Station
A facility, with instruments and equipment for measuring
atmospheric conditions to provide information on weather
along the network
6. Controller Cabinet
A cabinet, at the side of the road containing control
equipment associated with communication installations,
traffic signals and other road features.
7. ITS Asset Asset, related to the Intelligent Transport System, installed
along the network
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 22 / 82
Asset Category Asset Type/Dataset Asset Type Description
9. Electrification
System
1. Overhead line System that allow the transmission of electrical energy to
the train
2. Third rail Railway electrification system using a third rail located
alongside the track to supply DC power to the trains.
3. Transformer Electrical device that transfers electrical energy between
two or more circuits through electromagnetic induction
7.3 CONSTRUCTION DATA GROUP
This data group aims at identifying data related to the process either of building an asset (e.g. bridge) or of installing a new
asset (e.g. traffic camera) within the transportation network.
In order to consider the differences between the construction of an infrastructure asset and the mere installation of new
equipment, datasets included in this Data Group are the following two:
Asset Construction
Asset Installation
Table 7-9 Asset Construction Dataset
Code Name Description Data Type
10.1.1 Asset ID The unique asset identifier AN
10.1.2 Owner Owner of the asset A
10.1.3 Construction start date The start date for the construction process D
10.1.4 Construction end date The end date for the construction process D
10.1.5 Construction Manager Construction Manager Name A
10.1.6 Construction
Organisation Name
Construction Company name A
10.1.7 Design Organisation
Name
Design Company name A
10.1.8 Design Manager Design Manager Name A
10.1.9 Design start date The start date for the design process D
10.1.10 Design end date The end date for the design process D
10.1.11 Commissioner Name of the responsible for the commissioning of the asset A
10.1.12 Commissioning result Results of the commissioning process A
10.1.13 Commissioning Date Date of completion of commissioning process D
10.1.14 As Constructed Plan
Number
As Constructed drawing plan number AN
10.1.15 Project or contract Id
that created the asset
The project or contract Id that created the asset. AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 23 / 82
Code Name Description Data Type
10.1.16 Contractor or suppliers
Unique asset ID
The contractor or suppliers Unique ID for the asset AN
Table 7-10 Asset Installation Dataset
Code Name Description Data Type
10.2.1 Asset ID The unique asset identifier AN
10.2.2 Installation Date The start date for the construction process D
10.2.3 Commissioning Date Date of completion of commissioning process D
10.2.4 Commissioner Name of the responsible for the commissioning of the asset A
10.2.5 Commissioning result Results of the commissioning process A
10.2.6 Contractor or suppliers
Unique asset ID
The contractor or suppliers Unique ID for the asset AN
10.2.7 Project or contract Id
that created the asset
The project or contract Id that created the asset. AN
7.4 CONDITION & PERFORMANCE DATA GROUP
This data group relates to asset condition and performance information that can be used by a wide range of stakeholders to
rate the efficiency or effectiveness of how the asset is operating.
The following datasets are the representative ones for this category:
Asset Lifecycle: data to record life history of the asset;
Asset Performance: data to describe asset technical levels of service;
Asset Condition: data to describe the state of an asset at a particular instance in time. This data is usually capture by
inspection, survey or monitoring.
Asset Inspection: data to track the activity related to asset condition monitoring, that provides inputs to evaluate
asset condition
Table 7-11 Asset Lifecycle Dataset
Code Name Description Data Type
11.1.1 Asset ID Unique asset identifier AN
11.1.2 Out of service date The date the asset was taken out of service or replaced D
11.1.3 Life expected The number of years the asset is expected to provide service
(design life)
I
11.1.4 Life achieved The number of years the asset was in service I
11.1.5 Out of service date The date the asset was taken out of service or replaced D
11.1.6 Asset age The current age of the asset I
11.1.7 Remaining assessed life The assessed remaining life for the asset I
11.1.8 Remaining life assesing
method
The method applicated to asses the remaining life for an asset
(e.g through inspection, applying engeenering model, etc.)
A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 24 / 82
Code Name Description Data Type
11.1.9 Remaining life calculated Theoretical remaining life for the asset calculated as difference
between Life Expected and Current Asset Age
I
11.1.10 Remaining life assessing
date
Date when the assessment of remaining life has been performed D
Table 7-12 Asset Performance Dataset
Code Name Description Data Type
11.2.1 Asset ID Unique asset identifier AN
11.2.2 Technical performance
category
Category of performance (e.g. roughness, skid resistance, etc.) A
11.2.3 Performance required Required technical performance value AN
11.2.4 Performance
specification
The specification relating to the performance measure AN
11.2.5 Actual Performance Actual technical performance value AN
11.2.6 Performance achieved Achieved technical performance (in percentage) I
Table 7-13 Asset Condition Dataset
Code Name Description Data Type
11.3.1 Asset ID The unique asset identifier AN
11.3.2 Overall rating
A numerical rating of the impact of the current condition of an
asset on meeting its service objectives (1- Very Good, 2 - Good,
3 - Fair, 4 - Poor, 5 - Poor)
I
11.3.3 Rating Date Date referred to asset rating process execution D
11.3.4 Asset condition rating
distribution
Percent of asset at specific condition (for each possible rating
value) I
Pavement Condition Sub Dataset
11.3.5 Skid Resistance Skid resistance as characterised by the coefficient of friction. DC
11.3.6 Transverse profile The vertical deviations of the road surface from a horizontal
reference perpendicular to the lane direction DC
11.3.7 Longitudinal profile The perpendicular deviations of the road surface from an
established reference parallel to the lane direction DC
11.3.8 Ravelling Surface disintegration value DC
11.3.9 Pavement deflection Pavement deflection value at the test load. DC
11.3.10 Cracking
Pavement longitudinal/transverse/crocodile cracking. The
percentage of a 100m section where
longitudinal/transverse/crocodile cracking is evident in the
traffic lane
I
11.3.11 Roughness
Measurement of the unevenness of the pavement in the
direction of travel. It is measured in units of IRI (International
Roughness Index)
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 25 / 82
Code Name Description Data Type
11.3.12 Rutting
Rutting is a longitudinal surface depression in the wheelpath
measured as maximum perpendicular distance between the
bottom surface of a straightedge and the contact area of the
gauge with the road surface at a specified location
DC
11.3.13 Potholes Number of potholes (bowl-shaped holes of various sizes
occurring in the pavement surface) I
Road Marking Condition Sub Dataset
11.3.14 Retro reflectivity Measure of the ability of a road marking to reflect light from a
vehicle's headlights back to the driving position of a vehicle DC
11.3.15 Luminance Measure of the brightness of its colour DC
11.3.16 Skid resistance Skid resistance as characterised by the coefficient of friction. DC
Sign Condition Sub Dataset
11.3.17 Retroreflectivity Measure of the ability of a road marking to reflect light from a
vehicle's headlights back to the driving position of a vehicle DC
11.3.18 Luminance Measure of the brightness of its colour DC
Rail Condition Sub Dataset
11.3.19 Running surface wear Measure of the wear/attrition of the surface of rail DC
11.3.20 Break Breaks that can be present on a rail DC
11.3.21 Inclination Measure of the inclination of the rail DC
11.3.22 Corrosion Measure of the corrosion of rail through the corrosion rate DC
11.3.23 Discontinuities in the
running surface Type and measure of discontinuity that can be find on a rail DC
11.3.24 Buckling Buckling of rail due to heat DC
11.3.25 Corrugation Measure of the corrugation that can be present along the
surface of the rail DC
Overhead line Condition Sub Dataset
11.3.26 Position Vertical and lateral difference from the standard position of the
contact wire DC
11.3.27 Contact wire thickness The thickness of contact wire DC
11.3.28 Patches Abrasion patches at contact wire DC
Table 7-14 Asset Inspection Dataset
Code Name Description Data Type
11.4.1 Asset ID Unique asset identifier AN
11.4.2 Inspection ID Unique inspection identifier AN
11.4.3 Inspection Date Date when the inspection has been performed D
11.4.4 Inspection Type Type of inspection (e.g. periodical, expectional, major, minor,
etc) A
11.4.5 Inspection Status Current status of the inspection A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 26 / 82
Code Name Description Data Type
11.4.6 Inspection Owner Name of the person who performed the inspection A
7.5 RISK & SAFETY DATA GROUP
This data group relates to risk management practices through the collection of information useful to address asset
improvement/maintenance interventions.
The following datasets are the representative ones for this category:
Asset Risk: data to describe risks occurring on the asset like risk likelihood, impact, action to be implemented, etc.;
Asset Defect: data to record defects occurring on the asset, and their updates during time (e.g detection date of the
defect, defect closing date, asset defect rate, etc.).
Table 7-15 Asset Risk Dataset
Code Name Description Data Type
12.1.1 Asset ID Unique asset identifier AN
12.1.2 Risk ID Unique risk identifier AN
12.1.3 Risk Description Description of the risk A
12.1.4 Likelihood Likelihood of risk realization DC
12.1.5 Impact Risk impact level I
12.1.6 Risk level Evaluation of risk level I
12.1.7 Impact description Description of risk consequence A
12.1.8 Risk response Description of solutions/actions to mitigate the risk A
12.1.9 Risk Start date Notification date for the risk D
12.1.10 Risk End Date Closing date for the risk D
12.1.11 Risk Owner Person/Organization owner of the risk A
Table 7-16 Asset Defect Dataset
Code Name Description Data Type
12.2.1 Asset ID Unique asset identifier AN
12.2.2 Defect ID Unique defect identifier AN
12.2.3 Inspection ID Unique inspection identifier AN
12.2.4 Defect description A description of the identified defect A
12.2.5 Defect placement A description where the defect is present on the asset A
12.2.6 Defect Rate Percentage of the defect extension on the asset DC
12.2.7 Defect Gravity Evaluation of defect gravity DC
12.2.8 Defect Cause The cause for defect presence A
12.2.9 Defect Status Status of the defect A
12.2.10 Defect Detection Date Detection date for the defect D
12.2.11 Defect Closing Date Closing date for the defect D
7.6 MAINTENANCE DATA GROUP
This data group relates to asset maintenance practices in terms of interventions made or planned for the assets and related
costs. This data are useful for several purposes like to understand the asset condition, to perform a more accurate asset
valuation or to evaluate work effectiveness, etc.
The following datasets are the representative ones for this category:
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 27 / 82
Maintenance Work: data to record either the future intervention works and the history of what has been done to an
asset
Table 7-17 Maintenance Work Dataset
Code Name Description Data Type
13.1.1 Work ID Unique work identifier AN
13.1.2 Corridor ID Unique Corridor identifier AN
13.1.3 Start Milestone Starting Km of the work DC
13.1.4 End Milestone Ending Km of the work DC
13.1.5 Asset ID ID of assets involved in the work AN
13.1.6 Work Start Date Starting date for the work D
13.1.7 Work End Date Closing date for the work D
13.1.8 Work Status The status of the work (e.g. ongoing, planned, completed,
suspended,etc.) A
13.1.9 Work Progress Percentage of work completion DC
13.1.10 Work Description Description of the works to be carried out on the assets A
13.1.11 Work Type Work Category (e.g. Routine Maintenance, Preventive
Maintenance, Enhancement Maintenance) A
13.1.12 Work Activity Classification of work activity (e.g. cleaning,repairing, installing) A
13.1.13 Work estimated Cost Estimated cost for the work DC
13.1.14 Work Actual Cost The actual cost (planned or paid) for the maintenance work DC
13.1.15 Contractor ID Unique identifier for the contractor having the responsibility to
execute the works AN
13.1.16 Contract ID Reference Unique identifier for the contract AN
7.7 FINANCIAL & ACCOUNTING DATA GROUP
The following datasets are the representative ones for this category:
Asset Valuation: data referred to asset valuation process, in order to allow for example:
comparing same asset types on different network
driving strategic decision regarding network transportation development (e.g. new asset construction,
renewal of current assets,
evaluating performance of asset management practices based on improvement of asset value over time
Asset Expenditures: data referred to accounting process in order to have an overall monitoring of asset expenditures;
Asset Funds: data to describe funding model for asset management
Table 7-18 Asset Valuation Dataset
Code Name Description Data Type
14.1.1 Asset ID Unique asset identifier AN
14.1.2 Construction/Installation
date Date the asset was built or installed D
14.1.3 Unit cost Cost per unit of the asset DC
14.1.4 Operation status Current operational state of the asset (e.g. in use, dismissed,
removed) A
14.1.5 Estimate currency Currency used to estimate costs A
14.1.6 Asset valuation method Valuation method adopted (e.g. Historical Cost, Gross
Replacement Cost, Economic Value, etc.) A
14.1.7 Asset Value Estimated asset value DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 28 / 82
Code Name Description Data Type
14.1.8 Valuation date The date the valuation was undertaken D
Table 7-19 Asset Expenditures Dataset
Code Name Description Data Type
14.2.1 Asset ID Unique asset identifier AN
14.2.2 Expenditure ID Unique expenditure ID AN
14.2.3 Expenditure Value Amount of expenditure (planned or actual) DC
14.2.4 Expenditure currency Currency used for the costs A
14.2.5 Expenditure Type Capital or Operational type of expenditure for the Asset A
14.2.6 Category of Expenditure Categorization for the expenditure (e.g. building cost,
purchasing cost, installation cost, maintenance cost, etc.)
A
14.2.7 Expenditure Data The date when the expenditure was undertaken D
Table 7-20 Asset Funds Dataset
Code Name Description Data Type
14.3.1 Fund ID Unique Fund ID AN
14.3.2 Fund Value Amount of the fund DC
14.3.3 Fund Type Type of Fund (EU Fund, Private Fund, Government Fund, etc.) A
14.3.4 Fund Source Owner name of the Fund A
14.3.5 Fund currency Currency used for fund value A
14.3.6 Fund Date Date when the fund is delivered D
7.8 OPERATIONAL DATA GROUP
This data group relates to data directly linked with daily operations occurring along the transportation network. The datasets
identified in this data group are the following:
Asset Access Restriction: data to describe any specific (temporary or permanent) access restriction that can influence
the standard level of services performed by the network;
Asset Event: data to describe any relevant event occurring during network operations (e.g. car accidents, damaged
assets, presence of obstacles, etc.) that can provide input for other asset management practices (e.g. asset
maintenance, asset performance improvement, etc.);
Table 7-21 Asset Access Restriction Dataset
Code Name Description Data Type
15.1.1 Restriction ID Unique identification code for the restriction AN
15.1.2 Road ID Unique Road identifier AN
15.1.3 Start Milestone Starting Km of restriction DC
15.1.4 End Milestone Ending Km of the restriction DC
15.1.5 Asset ID Unique asset identifier, involved in the restriction (e.g. Bridge) AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 29 / 82
Code Name Description Data Type
15.1.6 Restriction type Restriction type (eg. Weight, Height, Direction, etc.) A
15.1.7 Restriction reason Reason for the restriction being applied (e.g. Cars, Pedestrians,
Buses, etc.)
A
15.1.8 Organisation responsible The organisation responsible for the asset causing the restriction A
15.1.9 Restriction status The status of the restriction (permanent or temporary) A
15.1.10 Restriction period The time period the restriction applies (Continuous or Periodic) A
15.1.11 Restriction start date The date the restriction starts D
15.1.12 Restriction end date The date the restriction ends D
Table 7-22 Asset Event Dataset
Code Name Description Data Type
15.2.1 Event ID Unique Event identifier AN
15.2.2 Event Type Classification of the event (e.g accident, weather condition,
presence of obstacles, etc. )
A
15.2.3 Event Description Description of the event occuring along the network A
15.2.4 Event Status Current status of the event (planned, on going, closed) A
15.2.5 Corridor ID The unique Corridor identifier where the asset is located AN
15.2.6 Start Milestone Starting Km of the event DC
15.2.7 End Milestone Ending Km of the event DC
15.2.9 Event Start Date The date the event starts D
15.2.10 Event End Date The date the event ends D
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 30 / 82
8 Conclusion
The design of an ADD has represented the first pillar to build a common approach for asset data management among NIAs.
During the study, the following key data groups have been identified (Figure 5-1. Asset Core Data Scheme):
Two core data groups (Network Location Referencing, Asset Inventory) to identify both the network topological
model and the asset register; within asset register, asset types should be characterized according to the network
type (e.g. road, rail or waterway);
Six data groups, which information could be common across transportation assets (Construction, Condition &
Performance, Risk & Safety, Maintenance, Financial & Accounting, Operational);
From identified data groups, ADD has been developed through the description of related datasets and data items and whose
final contents represent an organized index of assets information.
Aiming at capitalizing the ADD scheme, next step will be to design the functional and technical aspects of a possible Asset
Information Management System, an IT system that is able:
to extract all asset data present in several IT systems (data sources),
to aggregate and transform them according to a standard data model (derived from the ADD scheme)
to assure data reliability, integrity and univocity;
to publish selected data to provide useful information that could be shared within various asset stakeholders for asset
stakeholders;.
Next task 3.2 “Design of a Common Core-Model for Asset Information Management System” will therefore deliver a Business
Blueprint document, a detailed document about the scope, the specifications and the completeness of an IT solution
(requirements, processes, users, functions, architecture and so on) in order to obtain desired outcomes and benefits.
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 31 / 82
9 References
“Task Group N2 – Asset Management” - CEDR
“PAS 1192-2:2013 -Specification for information management for the capital/delivery phase of construction projects
using building information modelling” – BSI, 2013;
“PAS 1192-3:2014 - Specification for information management for the operational phase of assets using building
information modelling” – BSI, 2014;
“Asset Data Management Manual – Principles and Core Requirements” – Highways England, 2016;
“Data Standard for Road Management and Investment in Australia and New Zealand: Version 1” - Austroads, 2016;
“Highway Infrastructure Asset Management - Guidance Document” - UK Roads Liaison Group, 2013;
“Overall road asset performance Deliverable” - HeRoad, 2012;
“Equipment performance assessment” - HeRoad, 2012;
“Structures performance assessment” - HeRoad, 2012;
“Data Management for Road Administrations – A Best Practices Guide” - Western European Road Directors (WERD),
2003;
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 32 / 82
Annex I – Asset Inventory Datasets
The following table presents the ADD contents for the Asset Inventory Data Group:
Table 0-1 Asset Inventory Datasets
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
1. Asset Inventory - Carriageway
1. Pavement - 1.1.1 Asset ID The unique asset identifier AN
1. Asset Inventory - Carriageway
1. Pavement - 1.1.2 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
1. Pavement - 1.1.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
1. Pavement - 1.1.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
1. Pavement - 1.1.5 Pavement Type Type of Pavement (e.g. Flexible, Flexible Composite, Rigid Concrete, Rigid composite)
A
1. Asset Inventory - Carriageway
1. Pavement - 1.1.6 Number of lanes
Number of lanes. I
1. Asset Inventory - Carriageway
1. Pavement - 1.1.7 Start Milestone Starting Km of the asset DC
1. Asset Inventory - Carriageway
1. Pavement - 1.1.8 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
1. Pavement - 1.1.9 Length Length of Pavement, calculated as difference between End Milestone and Start Milestone
DC
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.10 Layer ID Unique ID Pavement Layer identifier
AN
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.11 Layer depth Depth of material for the layer DC
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.12 Layer material Type of material for the layer A
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.13 Layer number The order of the pavement layers from top (layer 1) to bottom
I
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.14 Layer type The type of layer A
1. Asset Inventory - Carriageway
1. Pavement Pavement Layer
1.1.15 Layer width Width of material for the layer DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 33 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.1 Asset identifier The unique asset identifier AN
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.2 Owner Owner of the asset A
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.3 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.4 Link ID Network link where the asset is placed
AN
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.7 Start Milestone Starting Km of the asset DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.8 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.9 Type Type of marking (Lane arrows, Continuos line,
A
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.10 Colour Colour of road marking A
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.11 Placement Position of road marking along carriageway (center, roadside, etc.)
A
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.12 Length Length of the road marking DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.13 Width Width of the line DC
1. Asset Inventory - Carriageway
2. Road Markings - 1.2.14 Paint Type Paint type used for the marking A
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.1 Asset identifier The unique asset identifier AN
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.2 Owner Owner of the asset A
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.3 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.4 Link ID Network link where the asset is placed
AN
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.7 Start Milestone Starting Km of the asset DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 34 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.8 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.9 Class Other, PROHIBITORY, WARNING/INFORMATORY
A
1. Asset Inventory - Carriageway
3. Road Stud - 1.3.10 Colour Colour of the road stud DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.1 Asset identifier The unique asset identifier AN
1. Asset Inventory - Carriageway
4. Kerb - 1.4.2 Owner Owner of the asset A
1. Asset Inventory - Carriageway
4. Kerb - 1.4.3 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
4. Kerb - 1.4.4 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.5 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.6 Start Milestone Starting Km of the asset DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.7 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.8 Material Material of which the asset is made of (e.g. Concrete, Extruded Asphalt, Natural Stone, Other)
A
1. Asset Inventory - Carriageway
4. Kerb - 1.4.9 Length Length DC
1. Asset Inventory - Carriageway
4. Kerb - 1.4.10 Type Kerb Type A
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.1 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.2 Link ID Network link where the asset is placed
AN
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.5 Start Milestone Starting Km of the asset DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.6 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.7 Shoulder Length Length of the shoulder DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.8 Shoulder Width Width of the shoulder DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.9 Shoulder Use Utilization of the shoulder (e.g. emergency lane, standing,etc.)
DC
1. Asset Inventory - Carriageway
5. Shoulder (Carriageway)
- 1.5.10 Shoulder type Type of Shoulder (e.g. paved, unpaved)
A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 35 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.1 Road ID The unique road identifier where the asset is located
AN
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.2 Link ID Network link where the asset is placed
AN
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.5 Start Milestone Starting Km of the asset DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.6 End Milestone Ending Km of the asset DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.10 Type Pathway type A
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.11 Width Pathway Width DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.12 Length Pathway Length DC
1. Asset Inventory - Carriageway
6. Foot/cycleway - 1.6.13 Material Pathway Material (e.g. concrete, asphalt, clay, etc.)
A
2. Asset Inventory - Track
1. Rail - 2.1.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
1. Rail - 2.1.2 Railway ID The unique road identifier where the asset is located
AN
2. Asset Inventory - Track
1. Rail - 2.1.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
2. Asset Inventory - Track
1. Rail - 2.1.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
2. Asset Inventory - Track
1. Rail - 2.1.5 Type of Rail The type of rail (Stock rail, switch rail, through rail, wing rail; check rail)
A
2. Asset Inventory - Track
1. Rail - 2.1.6 Start Milestone Starting Km of the asset DC
2. Asset Inventory - Track
1. Rail - 2.1.7 End Milestone Ending Km of the asset DC
2. Asset Inventory - Track
1. Rail - 2.1.8 Length Length calculated as difference between End Milestone and Start Milestone
DC
2. Asset Inventory - Track
2. Fastening 2.2.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
2. Fastening 2.2.2 Railway ID The unique road identifier where the asset is located
AN
2. Asset Inventory - Track
2. Fastening 2.2.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
2. Asset Inventory - Track
2. Fastening 2.2.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
2. Asset Inventory - Track
2. Fastening - 2.2.5 Material The type of material
A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 36 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
2. Asset Inventory - Track
3. Sleeper - 2.3.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
3. Sleeper - 2.3.2 Railway ID The unique road identifier where the asset is located
AN
2. Asset Inventory - Track
3. Sleeper - 2.3.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
2. Asset Inventory - Track
3. Sleeper - 2.3.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
2. Asset Inventory - Track
3. Sleeper - 2.3.5 Material The type of material
A
2. Asset Inventory - Track
3. Sleeper - 2.3.6 Height The Height of the sleeper
DC
2. Asset Inventory - Track
3. Sleeper - 2.3.7 Width Width of the sleeper
DC
2. Asset Inventory - Track
3. Sleeper - 2.3.8 Distance
Distance between two adjacent sleepers
DC
2. Asset Inventory - Track
4. Ballast - 2.4.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
4. Ballast - 2.4.2 Railway ID The unique road identifier where the asset is located
AN
2. Asset Inventory - Track
4. Ballast - 2.4.3 Superface
The surface of the extension of ballast DC
2. Asset Inventory - Track
4. Ballast - 2.4.4 Material The material of the ballast A
2. Asset Inventory - Track
5. Switch blades - 2.5.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
5. Switch blades - 2.5.2 Railway 1 ID The unique railway identifier of intersected railway no 1
AN
2. Asset Inventory - Track
5. Switch blades - 2.5.3 Railway 2 ID The unique railway identifier of intersected railway no 2
AN
2. Asset Inventory - Track
5. Switch blades - 2.5.4 Railway 3 ID The unique railway identifier of intersected railway no 3
AN
2. Asset Inventory - Track
5. Switch blades - 2.5.5 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
2. Asset Inventory - Track
5. Switch blades - 2.5.6 Material Blade Material A
2. Asset Inventory - Track
6. Point Machine - 2.6.1 Asset ID The unique asset identifier AN
2. Asset Inventory - Track
6. Point Machine - 2.6.2 Railway ID The unique railway identifier where the asset is located
AN
2. Asset Inventory - Track
6. Point Machine - 2.6.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.1 Railway ID The unique railway identifier where the asset is located
AN
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.2 Link ID Network link where the asset is placed
AN
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 37 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.5 Start Milestone Starting Km of the asset DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.6 End Milestone Ending Km of the asset DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.7 Shoulder Length Length of the shoulder DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.8 Shoulder Width Width of the shoulder DC
2. Asset Inventory - Track
7. Shoulder (Railway)
- 2.7.9 Shoulder type Type of Shoulder (e.g. paved, unpaved)
A
3. Asset Inventory - Earthworks
1. Embankments - 3.1.1 Corridor ID The unique Corridor identifier where the asset is located
AN
3. Asset Inventory - Earthworks
1. Embankments - 3.1.2 Link ID Network link where the asset is placed
AN
3. Asset Inventory - Earthworks
1. Embankments - 3.1.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.5 Start Milestone Starting Km of the asset DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.6 End Milestone Ending Km of the asset DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.7 Start Length Length of Embankment DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.8 Start Angle Angle of Embankment DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.9 End Length Length of Embankment DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.10 End Angle Angle of Embankment DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.11 Area Total Surface of Embankment DC
3. Asset Inventory - Earthworks
1. Embankments - 3.1.12 Soil type The soil type DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.13 Corridor ID The unique Corridor identifier where the asset is located
AN
3. Asset Inventory - Earthworks
2. Cutting - 3.2.14 Link ID Network link where the asset is placed
AN
3. Asset Inventory - Earthworks
2. Cutting - 3.2.15 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.16 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.17 Start Milestone Starting Km of the asset DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.18 End Milestone Ending Km of the asset DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 38 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
3. Asset Inventory - Earthworks
2. Cutting - 3.2.19 Start Length Length of Embankment DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.20 Start Angle Angle of Embankment DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.21 End Length Length of Embankment DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.22 End Angle Angle of Embankment DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.23 Area Total Surface of Embankment DC
3. Asset Inventory - Earthworks
2. Cutting - 3.2.24 Soil type The soil type A
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.25 Corridor ID The unique Corridor identifier where the asset is located
AN
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.26 Link ID Network link where the asset is placed
AN
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.27 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.28 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.29 Soil type The soil type A
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.30 Slope Area Area of slope face DC
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.31 Slope length This is the actual length of the slope measured from the start point to the end point
DC
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.32 Average height Average height of the slope DC
3. Asset Inventory - Earthworks
3. At-Grade - 3.3.33 Soil type The soil type A
4. Asset Inventory - Structure
1. Bridge - 4.1.1 Unique asset identifier
The unique asset identifier AN
4. Asset Inventory - Structure
1. Bridge - 4.1.2 Owner Owner of the asset A
4. Asset Inventory - Structure
1. Bridge - 4.1.3 Corridor ID The unique Corridor identifier where the asset is located
AN
4. Asset Inventory - Structure
1. Bridge - 4.1.4 Link ID Network link where the asset is placed
AN
4. Asset Inventory - Structure
1. Bridge - 4.1.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
4. Asset Inventory - Structure
1. Bridge - 4.1.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
4. Asset Inventory - Structure
1. Bridge - 4.1.7 Start Milestone Starting Km of the asset DC
4. Asset Inventory - Structure
1. Bridge - 4.1.8 End Milestone Ending Km of the asset DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 39 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
4. Asset Inventory - Structure
1. Bridge - 4.1.9 Bridge Function
The function the bridge provides whether it be for the passage of pedestrians, vehicles, rail, bicycles, or a combination of road users
A
4. Asset Inventory - Structure
1. Bridge - 4.1.10 Earthquake rating
Earthquake rating of the structure DC
4. Asset Inventory - Structure
1. Bridge - 4.1.11 Beam Material The material the beam is constructed of
A
4. Asset Inventory - Structure
1. Bridge - 4.1.12 Column or Pile Material
The material the column or pile is constructed of
A
4. Asset Inventory - Structure
1. Bridge - 4.1.13 Foundation type
Foundation type A
4. Asset Inventory - Structure
1. Bridge - 4.1.14 Foundation material
Foundation material A
4. Asset Inventory - Structure
1. Bridge - 4.1.15 Number of Beams
Number of Beams I
4. Asset Inventory - Structure
1. Bridge - 4.1.16 Number of Piers Number of Piers I
4. Asset Inventory - Structure
1. Bridge - 4.1.17 Number of columns or Piles
Number of columns or Piles I
4. Asset Inventory - Structure
1. Bridge - 4.1.18 Number of Spans
Number of spans of the bridge I
4. Asset Inventory - Structure
1. Bridge - 4.1.19 Length Total length of the structure in metres
DC
4. Asset Inventory - Structure
1. Bridge - 4.1.20 Width Total width of the structure in metres
DC
4. Asset Inventory - Structure
1. Bridge - 4.1.21 Vehicular Load Limit
Vehicular load limit on the structure.
DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.1 Unique asset identifier
The unique asset identifier AN
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.2 Owner Owner of the asset A
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.3 Corridor ID The unique Corridor identifier where the asset is located
AN
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.4 Link ID Network link where the asset is placed
AN
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.7 Start Milestone Starting Km of the asset DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.8 End Milestone Ending Km of the asset DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.9 Length of retaining wall
Length of the retaining wall DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.10 Average height Average height of the asset DC
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.11 Face area of wall
Face area of the wall A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 40 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
4. Asset Inventory - Structure
2. Retaining Wall
4.2.12 Face material Wall face material A
4. Asset Inventory - Structure
2. Retaining Wall - 4.2.13 Foundation type
Foundation type A
4. Asset Inventory - Structure
3. Tunnel - 4.3.1 Unique asset identifier
The unique asset identifier AN
4. Asset Inventory - Structure
3. Tunnel - 4.3.2 Owner Owner of the asset A
4. Asset Inventory - Structure
3. Tunnel - 4.3.3 Corridor ID The unique Corridor identifier where the asset is located
AN
4. Asset Inventory - Structure
3. Tunnel - 4.3.4 Link ID Network link where the asset is placed
AN
4. Asset Inventory - Structure
3. Tunnel - 4.3.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.7 Maximum trafficable height
Maximum trafficable height that can pass through the tunnel
DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.8 Start Milestone Starting Km of the asset DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.9 End Milestone Ending Km of the asset DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.10 Earthquake rating
Earthquake rating of the structure DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.11 Length Total length of the structure in metres
DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.12 Tunnel Structure Type
Structure Type (e.g. Overpass, Underpass, Arch)
A
4. Asset Inventory - Structure
3. Tunnel - 4.3.13 Tunnel Function
The function the tunnel provides whether it be for the passage of pedestrians, vehicles, rail, bicycles, or a combination of road users
A
4. Asset Inventory - Structure
3. Tunnel - 4.3.14 Number of emergency exits
The number of all emergency exits within the length of the tunnel
I
4. Asset Inventory - Structure
3. Tunnel - 4.3.15 Portal height Height of the portal DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.16 Portal width Width of the portal DC
4. Asset Inventory - Structure
3. Tunnel - 4.3.17 Portal material Material of the portal A
4. Asset Inventory - Structure
3. Tunnel TVCC 4.3.18 Rif. Cameras Refer to Asset Inventory - Equipment - Camera
A
4. Asset Inventory - Structure
3. Tunnel Automation System
4.3.19 Manufacturer Manufacturer of the system A
4. Asset Inventory - Structure
3. Tunnel Automation System
4.3.20 PLC Number of PLC controlled I
4. Asset Inventory - Structure
3. Tunnel Automation System
4.3.21 Supervisory computer
Number of supervisory computers I
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 41 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
4. Asset Inventory - Structure
3. Tunnel Automation System
4.3.22 Remote terminal unit
Number of terminal units I
4. Asset Inventory - Structure
3. Tunnel Ventilation System
4.3.24 Ventilation system type
Type of ventilation system (e.g. Longitudinal or Transverse)
A
4. Asset Inventory - Structure
3. Tunnel Ventilation System
4.3.25 Fans number Number of Fans installed I
4. Asset Inventory - Structure
3. Tunnel Ventilation System
4.3.26 Fan diameter Fan Diameter DC
4. Asset Inventory - Structure
3. Tunnel Ligthing 4.3.27 Lamps Refer to Asset Inventory - Lighting DC
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.28 Fire fighting system type
Type of fire fighting system (Deluge or Water Myst)
A
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.29 Water source Source of Water for the FFS A
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.30 Detection Method
Detection method (e.g. Linear heat, SCADA, etc.)
A
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.31 FFS discharge duration
Duration of FFS discharge I
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.32 Sprinklers number
Number of sprinklers I
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.33 Pipes number Number of pipes I
4. Asset Inventory - Structure
3. Tunnel Fire Fighting System
4.3.34 Pumps number Number of pumps I
5. Asset Inventory - Drainage
1. Culvert - 5.1.1 Unique asset identifier
The unique asset identifier AN
5. Asset Inventory - Drainage
1. Culvert - 5.1.2 Owner Owner of the asset A
5. Asset Inventory - Drainage
1. Culvert - 5.1.3 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
1. Culvert - 5.1.4 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
1. Culvert - 5.1.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
1. Culvert - 5.1.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
5. Asset Inventory - Drainage
1. Culvert - 5.1.7 Start Milestone Starting Km of the asset DC
5. Asset Inventory - Drainage
1. Culvert - 5.1.8 End Milestone Ending Km of the asset DC
5. Asset Inventory - Drainage
1. Culvert - 5.1.9 Number of Pipes
Number of the pipes I
5. Asset Inventory - Drainage
1. Culvert Pipe 5.1.10 Pipe section length
Pipe section length DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 42 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
5. Asset Inventory - Drainage
1. Culvert Pipe 5.1.11 Pipe material Pipe material (e.g. Brick, Concrete, Iron, etc.)
A
5. Asset Inventory - Drainage
1. Culvert Pipe 5.1.12 Pipe Diameter or Width
Internal pipe Diameter of the pipe or Width if the pipe is non-circular
D
5. Asset Inventory - Drainage
1. Culvert Pipe 5.1.13 Pipe type Pipe type A
5. Asset Inventory - Drainage
1. Culvert Pipe 5.1.14 Pipe Shape Shape of the pipe A
5. Asset Inventory - Drainage
2. Ditch - 5.2.1 Unique asset identifier
The unique asset identifier AN
5. Asset Inventory - Drainage
2. Ditch - 5.2.2 Owner Owner of the asset A
5. Asset Inventory - Drainage
2. Ditch - 5.2.3 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
2. Ditch - 5.2.4 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
2. Ditch - 5.2.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.7 Start Milestone Starting Km of the asset DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.8 End Milestone Ending Km of the asset DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.9 Length Ditch Length DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.10 Depth Ditch Depth DC
5. Asset Inventory - Drainage
2. Ditch - 5.2.11 Material Ditch Material A
5. Asset Inventory - Drainage
3. Manhole - 5.3.12 Owner Owner of the asset A
5. Asset Inventory - Drainage
3. Manhole - 5.3.13 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
3. Manhole - 5.3.14 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
3. Manhole - 5.3.15 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
3. Manhole - 5.3.16 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
5. Asset Inventory - Drainage
3. Manhole - 5.3.17 Material Manhole Material A
5. Asset Inventory - Drainage
3. Manhole - 5.3.18 Diameter Manhole Diameter DC
5. Asset Inventory - Drainage
3. Manhole - 5.3.19 Depth Manhole Depth DC
5. Asset Inventory - Drainage
4. Catch pits - 5.4.20 Unique asset identifier
The unique asset identifier AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 43 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
5. Asset Inventory - Drainage
4. Catch pits - 5.4.21 Owner Owner of the asset A
5. Asset Inventory - Drainage
4. Catch pits - 5.4.22 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
4. Catch pits - 5.4.23 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
4. Catch pits - 5.4.24 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
4. Catch pits - 5.4.25 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
5. Asset Inventory - Drainage
4. Catch pits - 5.4.26 Material Catch pits Material A
5. Asset Inventory - Drainage
4. Catch pits - 5.4.27 Diameter Catch pits Diameter DC
5. Asset Inventory - Drainage
4. Catch pits - 5.4.28 Depth Catch pits Depth DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.1 Unique asset identifier
The unique asset identifier AN
5. Asset Inventory - Drainage
5. Outfall - 5.5.2 Owner Owner of the asset A
5. Asset Inventory - Drainage
5. Outfall - 5.5.3 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
5. Outfall - 5.5.4 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
5. Outfall - 5.5.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.7 Start Milestone Starting Km of the asset DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.8 End Milestone Ending Km of the asset DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.9 Diameter Outfall diameter DC
5. Asset Inventory - Drainage
5. Outfall - 5.5.10 Material Outfall material DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.1 Unique asset identifier
The unique asset identifier AN
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.2 Owner Owner of the asset A
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.3 Road ID The unique road identifier where the asset is located
AN
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.4 Link ID Network link where the asset is placed
AN
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.5 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.6 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 44 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.7 Start Milestone Starting Km of the asset DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.8 End Milestone Ending Km of the asset DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.9 Length Filter drain length DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.10 Width Filter drain width DC
5. Asset Inventory - Drainage
6. Filter Drain - 5.6.11 Material Filter drain material A
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.1 Asset ID The unique asset identifier AN
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.2 Corridor ID The unique Corridor identifier where the asset is located
AN
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.4 Referring Milestone
Referring Road Km where the asset is located
DC
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.5 Column Type Type of Lighting column (e.g. High Mast, Column, Other)
A
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.6 Column Material
Material of which the column is made of
A
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.7 Mounting Height
Mounting Height DC
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.8 Mounting Bracket
Mounting Bracket A
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.9 Column Bracket Column Bracket A
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.10 Number Of Brackets
Number Of Brackets I
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.11 Number of Lamps
Number of Lamps I
6. Asset Inventory - Lighting
1. Lighting Column
- 6.1.12 Lighting Type Type of Lighting
A
6. Asset Inventory - Lighting
2. Lighting Unit - 6.2.1 Asset ID The unique asset identifier AN
6. Asset Inventory - Lighting
2. Lighting Unit - 6.2.2 Corridor ID The unique Corridor identifier where the asset is located
AN
6. Asset Inventory - Lighting
2. Lighting Unit - 6.2.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
6. Asset Inventory - Lighting
2. Lighting Unit - 6.2.4 Referring Milestone
Referring Road Km where the asset is located
DC
6. Asset Inventory - Lighting
2. Lighting Unit Lamp 6.2.5 Lamp Type Type of Lamp A
6. Asset Inventory - Lighting
2. Lighting Unit Lamp 6.2.6 Lamp Max Wattage
Max Wattage for the Lamp I
6. Asset Inventory - Lighting
2. Lighting Unit Lamp 6.2.7 Lamp Manufacturer
Lamp Brand A
6. Asset Inventory - Lighting
2. Lighting Unit Lantern 6.2.8 Lantern Manufacturer
Lantern Manufacturer A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 45 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
6. Asset Inventory - Lighting
2. Lighting Unit Lantern 6.2.9 Lantern Model Reference
Lantern Model Reference A
6. Asset Inventory - Lighting
2. Lighting Unit Lantern 6.2.10 Lantern Setting Lantern Setting A
6. Asset Inventory - Lighting
2. Lighting Unit Lantern 6.2.11 Lantern Protection
Lantern Protection A
7. Asset Inventory - Furniture
1. Barrier - 7.1.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
1. Barrier - 7.1.2 Road ID The unique road identifier where the asset is located
AN
7. Asset Inventory - Furniture
1. Barrier - 7.1.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.7 Length of barrier
Length of the barrier in metres DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.8 Material of the barrier rail
Material of the barrier rail A
7. Asset Inventory - Furniture
1. Barrier - 7.1.9 Barrier Type Type of Barrier (Noise Barrier, Safety Barrier, Pedestrian Barrier, New Jersey Barrier, etc.)
A
7. Asset Inventory - Furniture
1. Barrier - 7.1.10 Height of barrier
Height of the road barrier measured from the ground surface
DC
7. Asset Inventory - Furniture
1. Barrier - 7.1.11 Paint Colour Paint colour of the barrier A
7. Asset Inventory - Furniture
1. Barrier - 7.1.12 Barrier number of posts
Number of posts in the barrier I
7. Asset Inventory - Furniture
1. Barrier - 7.1.13 Ground fixed method
How the barrier is fixed to the ground
A
7. Asset Inventory - Furniture
1. Barrier - 7.1.14 Rail width Rail width DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
2. Billboard - 7.2.2 Road ID The unique road identifier where the asset is located
AN
7. Asset Inventory - Furniture
2. Billboard - 7.2.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.7 Billboard width Width of the billboard DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 46 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
7. Asset Inventory - Furniture
2. Billboard - 7.2.8 Billboard height Height of the billboard DC
7. Asset Inventory - Furniture
2. Billboard - 7.2.9 Billboard Material
Material of the billboard A
7. Asset Inventory - Furniture
2. Billboard - 7.2.10 Number of posts
Number of billboard posts I
7. Asset Inventory - Furniture
2. Billboard - 7.2.11 Post Material Material of the billboard post A
7. Asset Inventory - Furniture
3. Fence - 7.3.1 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
3. Fence - 7.3.2 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
3. Fence - 7.3.3 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
3. Fence - 7.3.4 Type Fence type A
7. Asset Inventory - Furniture
3. Fence - 7.3.5 Function Fence function (e.g. Agriculture, Security, Perimeter
A
7. Asset Inventory - Furniture
3. Fence - 7.3.6 Length Fence Length DC
7. Asset Inventory - Furniture
3. Fence - 7.3.7 Height Fence Height DC
7. Asset Inventory - Furniture
3. Fence - 7.3.8 Material Fence Material A
7. Asset Inventory - Furniture
4. Gate - 7.4.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
4. Gate - 7.4.2 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
4. Gate - 7.4.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
4. Gate - 7.4.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
4. Gate - 7.4.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
4. Gate - 7.4.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
4. Gate - 7.4.7 Length Length of the Gate DC
7. Asset Inventory - Furniture
4. Gate - 7.4.8 Gate Type Type of Gate (Snow Gate, Fence Gate, Carriageway Gate)
A
7. Asset Inventory - Furniture
5. Level Crossing - 7.5.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
5. Level Crossing - 7.5.2 Railway ID The unique railway identifier where the asset is located
AN
7. Asset Inventory - Furniture
5. Level Crossing - 7.5.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
5. Level Crossing - 7.5.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 47 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
7. Asset Inventory - Furniture
5. Level Crossing - 7.5.5 Type Type of level crossing (depending from the nation)
A
7. Asset Inventory - Furniture
6. Marker Post - 7.6.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
6. Marker Post - 7.6.2 Road ID The unique road identifier where the asset is located
AN
7. Asset Inventory - Furniture
6. Marker Post - 7.6.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
7. Asset Inventory - Furniture
6. Marker Post - 7.6.4 Referring Milestone
Referring Road Km where the asset is located
DC
7. Asset Inventory - Furniture
6. Marker Post - 7.6.5 Colour Colour of the Marker Post A
7. Asset Inventory - Furniture
6. Marker Post - 7.6.6 Material Material of the Marker Post A
7. Asset Inventory - Furniture
7. Pole - 7.7.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
7. Pole - 7.7.2 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
7. Pole - 7.7.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
7. Asset Inventory - Furniture
7. Pole - 7.7.4 Referring Milestone
Referring Road Km where the asset is located
DC
7. Asset Inventory - Furniture
7. Pole - 7.7.5 Pole height Pole height from the ground surface
DC
7. Asset Inventory - Furniture
7. Pole - 7.7.6 Pole Material Pole Material type A
7. Asset Inventory - Furniture
7. Pole - 7.7.7 Foundation type
Foundation type of the pole A
7. Asset Inventory - Furniture
7. Pole - 7.7.8 Pole attachments present
Pole attachments present A
7. Asset Inventory - Furniture
8. Sign - 7.8.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
8. Sign - 7.8.2 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
8. Sign - 7.8.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
8. Sign - 7.8.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
8. Sign - 7.8.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
8. Sign - 7.8.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
8. Sign - 7.8.7 Sign Type Sign type/category A
7. Asset Inventory - Furniture
8. Sign - 7.8.8 Sign Shape Shape of the sign (Round, Square, etc.)
A
7. Asset Inventory - Furniture
8. Sign - 7.8.9 Sign Width Total width of the sign DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 48 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
7. Asset Inventory - Furniture
8. Sign - 7.8.10 Number of sign panels
Number of panels in the sign I
7. Asset Inventory - Furniture
8. Sign - 7.8.11 Wording on Sign Wording on the sign (if present) A
7. Asset Inventory - Furniture
8. Sign - 7.8.12 Background colour
Background colour A
7. Asset Inventory - Furniture
8. Sign - 7.8.13 Background material
Background material A
7. Asset Inventory - Furniture
8. Sign - 7.8.14 Ground height Height from ground to bottom of the sign panel
A
7. Asset Inventory - Furniture
8. Sign - 7.8.15 Sign manufacturer
Sign manufacturer A
7. Asset Inventory - Furniture
8. Sign - 7.8.16 Number of posts
Number of sign posts I
7. Asset Inventory - Furniture
8. Sign - 7.8.17 Post Material Material of the sign post A
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.2 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.7 Material Gantry Material A
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.8 Height Gantry height DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.9 Width Structure Width DC
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.10 Number of Sign Panels
Number of Sign Panels I
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.11 Number of Columns
Number of Columns I
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.12 Foundation material
Foundation material A
7. Asset Inventory - Furniture
9. Sign Gantry - 7.9.13 Foundation type
Foundation type of the gantry A
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.1 Asset ID The unique asset identifier AN
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.2 Corridor ID The unique Corridor identifier where the asset is located
AN
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 49 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.5 Start Milestone Starting Km of the asset DC
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.6 End Milestone Ending Km of the asset DC
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.7 Length Hedge Length DC
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.8 Type Tree species A
7. Asset Inventory - Furniture
10. Vegetation (Tree /Hedge)
- 7.10.9 Height Tree / Hedge Height DC
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.1 Asset ID The unique asset identifier AN
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.2 Road ID The unique road identifier where the asset is located
AN
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.4 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.5 Manufacturer Brand A
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.6 Model Model A
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.8 Dimensions SOS Pillar dimension (WxHxD) DC
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.9 Weight SOS Pillar Weight DC
8. Asset Inventory - Equipment
1. SOS Pillar - 8.1.10 Status Information if SOS Pillar is active or not
B
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.1 Asset ID The unique asset identifier AN
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.2 Road ID The unique road identifier where the asset is located
AN
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.3 Pole /Sign Gantry ID
The pole/sign gantry identifier where camera is placed
DC
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.4 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.5 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.6 Camera Type The type of camera (Dome, Fixed, Speed)
A
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.7 Camera Size Size of the Camera DC
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.8 Manufacturer Camera Brand A
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.9 Model Number Camera model AN
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.10 Serial Number Camera serial number AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 50 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.11 Status Information if the camera is active or not
A
8. Asset Inventory - Equipment
2. Traffic Camera - 8.2.12 ITS Asset ID The unique ITS asset identifier AN
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.1 Corridor ID The unique Corridor identifier where the asset is located
AN
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.2 Pole /Sign Gantry ID
The pole/sign gantry identifier where camera is placed
DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.4 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.5 Manufacturer Manufacturer of the signal A
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.6 Model number Model number AN
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.7 Signal Type Type of Traffic Signal (e.g. Pedestrian, Traffic, etc.)
A
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.8 Luminaire size Size of the luminaire DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.9 Luminaire type Type of Luminarie DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.10 Lamp Type Type of lamp mounted on traffic signal
A
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.11 Controller ID Traffic Signal controller ID AN
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.12 Target board size
Target board size DC
8. Asset Inventory - Equipment
3. Traffic Signal - 8.3.13 Status Information if traffic signal is active or not
A
8. Asset Inventory - Equipment
4. VMS - 8.4.1 Asset ID The unique asset identifier AN
8. Asset Inventory - Equipment
4. VMS - 8.4.2 Road ID The unique road identifier where the asset is located
AN
8. Asset Inventory - Equipment
4. VMS - 8.4.3 Pole /Sign Gantry ID
The pole/sign gantry identifier where camera is placed
DC
8. Asset Inventory - Equipment
4. VMS - 8.4.4 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
4. VMS - 8.4.5 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
4. VMS - 8.4.6 VMS Type Description regarding the type of VMS
A
8. Asset Inventory - Equipment
4. VMS - 8.4.7 VMS display size Dimension of VMS display DC
8. Asset Inventory - Equipment
4. VMS - 8.4.8 VMS Overall dimension
Overall Dimension of VMS DC
8. Asset Inventory - Equipment
4. VMS - 8.4.9 VMS weight Weight of VMS DC
8. Asset Inventory - Equipment
4. VMS - 8.4.10 Manufacturer VMS Brand A
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 51 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
8. Asset Inventory - Equipment
4. VMS - 8.4.11 Model Number VMS model AN
8. Asset Inventory - Equipment
4. VMS - 8.4.12 Serial Number VMS serial number AN
8. Asset Inventory - Equipment
4. VMS - 8.4.13 Status Information if VMS is active or not A
8. Asset Inventory - Equipment
4. VMS - 8.4.14 ITS Asset ID The unique ITS asset identifier AN
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.1 Asset ID The unique asset identifier AN
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.2 Corridor ID The unique Corridor identifier where the asset is located
AN
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.3 Pole /Sign Gantry ID
The pole/sign gantry identifier where camera is placed
DC
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.4 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.5 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.6 Manufacturer Weather station Brand A
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.7 Model Number Weather station model AN
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.8 Serial Number Weather station serial number AN
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.9 Status Information if the station is active or not
A
8. Asset Inventory - Equipment
5. Weather Station
- 8.5.10 ITS Asset ID The unique ITS asset identifier AN
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.1 Asset ID The unique asset identifier AN
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.2 Corridor ID The unique Corridor identifier where the asset is located
AN
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.3 Owner Asset owner A
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.4 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.5 Referring Milestone
Referring Road Km where the asset is located
DC
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.6 Manufacturer Brand A
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.7 Model Model A
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.8 Dimensions Cabinet dimension (WxHxD) DC
8. Asset Inventory - Equipment
6. Controller Cabinet
- 8.6.9 ITS Asset ID The unique ITS asset identifier AN
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.1 ITS Asset ID The unique ITS asset identifier AN
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.2 Corridor ID
The unique corridor identifier where the asset is located
AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 52 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.3
X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.4
X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.5 Start Milestone Starting Km of the asset DC
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.6 End Milestone Ending Km of the asset DC
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.7 Type
Asset ITS component type (eg. CCTV, traffic sensor, weather station)
A
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.8
Access Requirements
The type of access requirements (eg. Traffic management)
A
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.9 Power source The type of power source (eg. Battery, power generator, solar)
A
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.10 Manufacturer The manufacturer of the asset ITS A
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.11
Data logger present
Whether a data logger is present or not
B
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.12 Communication method
The type of communication (eg. Bluetooth, microwave)
A
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.13
UPS is connected
Whether a UPS Is connected or not B
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.14 IP address The IP address of the asset AN
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.15 Model number The model number of the component of the asset
AN
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.16 Serial number
The serial number of the component of the asset
AN
8. Asset Inventory - Equipment
7. ITS Asset - 8.7.17
Control system type
The type of control system (Open-loop control, closed-loop control, feedback control, …)
A
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.1 Asset ID The unique asset identifier AN
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.2 Railway ID The unique road identifier where the asset is located
AN
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.5 Start Milestone Starting Km of the asset DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.6 End Milestone Ending Km of the asset DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.7 Length Length calculated as difference between End Milestone and Start Milestone
DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 53 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.8 Height The height of the wire from the rail DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.9 Number of wires
Number of contact wires I
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.10 Path The type of path of wires A
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.11 Amperage Current Amperage DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.12 Voltage Current Voltage DC
9. Asset Inventory - Electrification system
1. Overhead line - 9.1.13 Frequence Current Frequence DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.1 Asset ID The unique asset identifier AN
9. Asset Inventory - Electrification system
2. Third rail - 9.2.2 Railway ID The unique road identifier where the asset is located
AN
9. Asset Inventory - Electrification system
2. Third rail - 9.2.3 X,Y,Z coordinate start
The X,Y,Z coordinate locator point that defines the beginning of the asset
DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.4 X,Y,Z coordinate end
The X,Y,Z coordinate locator point that defines the end of the asset
DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.5 Start Milestone Starting Km of the asset DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.6 End Milestone Ending Km of the asset DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.7 Type of Rail The type of rail (Stock rail, switch rail, through rail, wing rail; check rail)
A
9. Asset Inventory - Electrification system
2. Third rail - 9.2.8 Length Length calculated as difference between End Milestone and Start Milestone
DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.9 Amperage Current Amperage DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.10 Voltage Current Voltage DC
9. Asset Inventory - Electrification system
2. Third rail - 9.2.11 Frequence Current Frequence DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.1 Asset ID The unique asset identifier AN
9. Asset Inventory - Electrification system
3. Transformer - 9.3.2 Railway ID The unique railway identifier where the asset is located
AN
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 54 / 82
Data Group Dataset Data Item
ID1 Asset Category ID2 Asset Type Sub Data
set Code Name Description
Data
Type
9. Asset Inventory - Electrification system
3. Transformer - 9.3.3 X,Y,Z coordinate The X,Y,Z coordinate locator point that defines the asset
DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.4 Amperage Current Amperage DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.5 Voltage Current Voltage DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.6 Frequence Current Frequence DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.7 Dimensions Dimensions of transformer DC
9. Asset Inventory - Electrification system
3. Transformer - 9.3.8 Weight Weight of transformer DC
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 55 / 82
Annex II – Asset Data Dictionary
The following file represents the full version of Asset Data Dictionary, that includes all datasets presented in the document.
ADD_Dataset.pdf
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 56 / 82
Annex III - Survey on Asset Data Management Practices
GENERAL CONTEXT
What kind of transport infrastructure network does the organization
manage? What is its extension?
Type Extension (#km) Sub category
☐ Road (e.g. toll motorways, highways, urban roads,
national roads, etc.)
☐ Rail
☐ Air
☐ Water
☐ Other (please specify)
What is the responsibility related to assets?
☐ Ownership
☐ Concession
Optional additional comments:
Which are the processes related to asset management for whom the
organization is responsible for?
☐ Design
☐ Build
☐ Maintain
☐ Enhance
☐ Operate
Optional additional comments:
Concerning asset management framework:
a) At which stage can be considered the development of strategies, objectives, policies
or procedures related to Asset Management:
☐ Initial
☐ On course preliminary
☐ On course advanced
☐ Completed
b) Which standards have been considered to design the model?
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 57 / 82
☐ ISO 55000
☐ PAS 1192
☐ ISO/TS 8000
☐ PAS 55
☐ BS 1192
☐ Other
If Other, please specify: _________________________
c) Describe briefly the contents of current AM framework adopted by the organization:
[Free Text]
ASSET INFORMATION MODEL
Which are the asset information domains covered by IT Systems?
Main Domain Sub Domain
☐ Legal ☐ Asset related contractual information
☐ Risk assessment and control measures
☐ Safety/Environmental information
☐ Other, please specify: __________________
☐ Financial ☐ Construction Costs
☐ Purchase/Leasing costs
☐ Maintenance/Operating costs
☐ Asset replacement value
☐ Downtime impact
☐ Whole life / Historical cost
☐ Other, please specify: __________________
☐ Technical ☐ Engineering data
☐ Operational Data (e.g. technical performance characteristics, design limits)
☐ Details of Asset Dependencies and interdependencies
☐ Design parameters
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 58 / 82
☐ Commissioning Data
☐ Other, please specify: __________________
☐ Managerial ☐ Asset identification numbers
☐ Asset location (e.g. spatial referencing, geographical information systems)
☐ Warranties and guarantee periods
☐ Maintenance and inspection data
☐ Emergency Plan
☐ Work schedules
☐ Asset related standards, processes and procedures
☐ Details of historical asset failures, causes and consequences
☐ Other, please specify: __________________
☐ Commercial ☐ Condition and performance targets/standards
☐ Utilization Data
☐ KPI
☐ Level of Services
☐ Other, please specify: __________________
For the information managed through IT Systems, please rate the
completeness of collected data compared to the entire transportation network:
Domain Level of completeness (1 high to 5 low)
Legal ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Financial ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Technical ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Managerial ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Commercial ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 59 / 82
What are the implemented IT systems that support asset information
management?
☐ Work Programme Planning and scheduling systems
☐ Document Management Systems
☐ Purchasing Systems
☐ Maintenance Systems
☐ Property Systems
☐ Accounting and financial planning systems
☐ Materials management and spares inventory systems
☐ Engineering design and modelling systems
☐ Performance reporting systems
☐ Condition monitoring systems
☐ Traffic Management Systems
☐ Knowledge management systems
☐ Other, please specify: ___________________
Concerning the presence of a Common Data Environment (CDE -Single
Source of Information for any given asset, used to collect, manage and dissiminate all
relevant approved files, documents, and data for multi-disciplinary teams in a managed
process), please define:
a) At which stage is the overall process of implementation of CDE?
☐ Initial
☐ On course preliminary
☐ On course advanced
☐ Completed
b) Which information domains, does the implemented CDE contain? In case not
implemented yet, please indicate the integration targets:
☐ Legal
☐ Financial
☐ Technical
☐ Managerial
☐ Institutional
☐ Other
If Other, please specify: _________________________
c) Which Asset Management decision processes the CDE currently supports?
☐ Project Selection ☐ Budgeting
☐ Strategic Investments ☐ Performance evaluation and monitoring
☐ Reporting and External Communication ☐ Other
If Other, please specify: _________________________
Did the organisation develop an Asset Data Dictionary in order to deploy
a common language regarding infrastructure’s assets?
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 60 / 82
☐ Yes ☐ No
Optional additional comments:
Which is the strategy adopted by the organization to perform a
reliable data integration between several data sources? Has a Master Data Management
methodology been applied?
ASSET DATA MANAGEMENT
Regarding asset data management procedures, please define:
a) Which formal procedures has the organization implemented?
☐ Data Collection and Maintenance
☐ Data Storage and Retrieval
☐ Other
If Other, please specify: _________________________
☐ Data Sharing and Exchange
☐ Data Quality
Optional additional comments:
b) For Data Quality assurance/control, which solutions have been implemented?
☐ Periodical Analysis/Audit
☐ Use of Automatic procedures
☐ Third Party Software solutions
☐ Other
If Other please specify:________________________
c) For Data collection, which roadway asset types are involved? Which is the adopted
method to perform the activity? (in case of different transportation network, please
integrate/modify the asset types)
Asset Type Data collection method
☐ Pavements ☐ Automatic
☐ Manual
☐ Both
☐ Structure (e.g. Bridges, Tunnels, Underpass, etc.) ☐ Automatic
☐ Manual
☐ Both
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 61 / 82
☐ Equipment (VMS, traffic camera, etc.) ☐ Automatic
☐ Manual
☐ Both
☐ Other Items (e.g. road signs, safety barriers, etc.) ☐ Automatic
☐ Manual
☐ Both
Optional additional comments:
Did the organization identify a data owner for each asset data
group?
☐ Yes
☐ No
Optional additional comments:
Regarding Asset Data sharing:
a) Which Entities can be considered as the main organization’s stakeholders for
information exchange regarding managed transportation network?
☐ Government
☐ Other Transportation Company (same managed network
type)
☐ Regional / Local Authorities
☐ Other Transportation Company (different managed
network type)
☐ Other
If Other please specify:________________________
b) Which key datasets does the organization disseminate? Please indicate, if present, the relevant ones for
multimodality purposes.
[Free Text]
ASSET DATA CLASSIFICATION
Regarding asset inventory, please indicate, choosing from the following,
the key asset categories managed through IT Systems
Main Category Sub Category
☐ Carriageway ☐ Flexible Pavement
☐ Flexible composite pavement
☐ Rigid Concrete Pavement
☐ Road Markings
☐ Road Stud
☐ Other, please specify: ______________
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 62 / 82
☐ Rigid Composite Pavement
☐ Kerbs
☐ Structure ☐ Bridge
☐ Tunnel
☐ Underpass
☐ Retaining Wall
☐ Culvert
☐ Drainage
☐ Viaduct
☐ Other, please specify: ______________
☐ Lighting ☐ Lighting Column
☐ High mast lighting
☐ Lighting unit attached to wall/pole
☐ Other, please specify: __________________
☐ Road Furniture ☐ Road Sign
☐ Safety Barrier
☐ Noise Barrier
☐ Safety Barrier
☐ Pedestrian Barrier
☐ Billboard
☐ Verge Marker Post
☐ Bus Shelter
☐ Toll Station
☐ Sign Gantry
☐ Gate
☐Other, please specify: _____________
☐ Equipment ☐ Traffic Camera/Sensor
☐ Weather Station
☐ VMS
☐ Ventilation System
☐ Traffic Signal
☐ SOS Pillar
☐ Fire Fighting System
☐ Wi-Fi System
☐Other, please specify: _____________
SURVEY REPLY BY HIGHWAYS ENGLAND
GENERAL CONTEXT
What kind of transport infrastructure network does the
organization manage? What is its extension?
Type Extension (#km) Sub category
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 63 / 82
☒ Road (e.g. toll motorways, highways, urban roads,
national roads, etc.)
☐ Rail
☐ Air
☐ Water
☐ Other (please specify)
What is the responsibility related to assets?
☒ Ownership
☐ Concession
Optional additional comments:
Which are the processes related to asset management for whom the
organization is responsible for?
☒ Design
☒ Build
☒ Maintain
☒ Enhance
☒ Operate
Optional additional comments:
Concerning asset management framework:
d) At which stage can be considered the development of strategies, objectives, policies
or procedures related to Asset Management:
☐ Initial
☒ On course preliminary
☒ On course advanced
☐ Completed
e) Which standards have been considered to design the model?
☒ ISO 55000
☐ PAS 1192
☐ ISO/TS 8000
☒ PAS 55
☐ BS 1192
☐ Other
If Other, please specify: _________________________
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 64 / 82
f) Describe briefly the contents of current AM framework adopted by the organization:
Highways England operates an asset management framework that has evolved over several decades. Whilst, the processes
we currently use are adequate, we are in the process of consolidating our asset management framework. This includes
our handling of asset data, which is comprehensive but disparate.
ASSET INFORMATION MODEL
Which are the asset information domains covered by IT Systems?
Main Domain Sub Domain
☒ Legal ☐ Asset related contractual information
☒ Risk assessment and control measures
☒ Safety/Environmental information
☐ Other, please specify: __________________
☒ Financial ☒ Construction Costs
☐ Purchase/Leasing costs
☒ Maintenance/Operating costs
☒ Asset replacement value
☒ Downtime impact
☒ Whole life / Historical cost
☐ Other, please specify: __________________
☒ Technical ☒ Engineering data
☒ Operational Data (e.g. technical performance characteristics, design limits)
☐ Details of Asset Dependencies and interdependencies
☒ Design parameters
☒ Commissioning Data
☐ Other, please specify: __________________
☒ Managerial ☒ Asset identification numbers
☒ Asset location (e.g. spatial referencing, geographical information systems)
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 65 / 82
☒ Warranties and guarantee periods
☒ Maintenance and inspection data
☒ Emergency Plan
☐ Work schedules
☒ Asset related standards, processes and procedures
☒ Details of historical asset failures, causes and consequences
☐ Other, please specify: __________________
☒ Commercial ☒ Condition and performance targets/standards
☒ Utilization Data
☒ KPI
☒ Level of Services
☐ Other, please specify: __________________
For the information managed through IT Systems, please rate the
completeness of collected data compared to the entire transportation network:
Domain Level of completeness (1 high to 5 low)
Legal ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Financial ☐ 1 ☐ 2 ☒ 3 ☐ 4 ☐ 5
Technical ☐ 1 ☐ 2 ☒ 3 ☐ 4 ☐ 5
Managerial ☐ 1 ☐ 2 ☐ 3 ☒ 4 ☐ 5
Commercial ☐ 1 ☐ 2 ☐ 3 ☒ 4 ☐ 5
What are the implemented IT systems that support asset information
management?
☐ Work Programme Planning and scheduling systems
☒ Document Management Systems
☒ Purchasing Systems
☒ Maintenance Systems
☐ Property Systems
☒ Materials management and spares inventory systems
☒ Engineering design and modelling systems
☒ Performance reporting systems
☒ Condition monitoring systems
☒ Traffic Management Systems
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 66 / 82
☒ Accounting and financial planning systems ☐ Knowledge management systems
☐ Other, please specify: ___________________
Concerning the presence of a Common Data Environment (CDE -Single
Source of Information for any given asset, used to collect, manage and dissiminate all
relevant approved files, documents, and data for multi-disciplinary teams in a managed
process), please define:
d) At which stage is the overall process of implementation of CDE?
☒ Initial
☐ On course preliminary
☐ On course advanced
☐ Completed
e) Which information domains, does the implemented CDE contain? In case not
implemented yet, please indicate the integration targets:
☐ Legal
☐ Financial
☒ Technical
☐ Managerial
☐ Institutional
☐ Other
If Other, please specify: The integrated asset management system is a work in progress. Highways England operates a
number of separate databases, which contain elements of the domains listed above.
f) Which Asset Management decision processes the CDE currently supports?
☐ Project Selection ☐ Budgeting
☒ Strategic Investments ☒ Performance evaluation and monitoring
☐ Reporting and External Communication ☐ Other
If Other, please specify: As above, it is expected that the new integrated asset management system will support all of these
decision processes, but it is not yet fully implemented.
Did the organisation develop an Asset Data Dictionary in order to deploy
a common language regarding infrastructure’s assets?
☒ Yes ☐ No
Optional additional comments: Provided by email on 31/10/16
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 67 / 82
Which is the strategy adopted by the organization to perform a
reliable data integration between several data sources? Has a Master Data Management
methodology been applied?
Not yet.
ASSET DATA MANAGEMENT
Regarding asset data management procedures, please define:
a) Which formal procedures has the organization implemented?
☒ Data Collection and Maintenance
☒ Data Storage and Retrieval
☐ Other
If Other, please specify: _________________________
☐ Data Sharing and Exchange
☒ Data Quality
Optional additional comments:
b) For Data Quality assurance/control, which solutions have been implemented?
☒ Periodical Analysis/Audit
☐ Use of Automatic procedures
☐ Third Party Software solutions
☐ Other
If Other please specify:________________________
c) For Data collection, which roadway asset types are involved? Which is the adopted
method to perform the activity? (in case of different transportation network, please
integrate/modify the asset types)
Asset Type Data collection method
☒ Pavements ☐ Automatic
☐ Manual
☒ Both
☒ Structure (e.g. Bridges, Tunnels, Underpass, etc.) ☐ Automatic
☐ Manual
☒ Both
☒ Equipment (VMS, traffic camera, etc.) ☐ Automatic
☐ Manual
☒ Both
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 68 / 82
☒ Other Items (e.g. road signs, safety barriers, etc.) ☐ Automatic
☐ Manual
☒ Both
Optional additional comments: All assets are surveyed automatically, but the complexity and use of automatic survey data
varies. For pavements, traffic speed surveying is carried out periodically and condition data is used to identify schemes
for maintenance, at which point manual surveys are carried out. For other assets, traffic speed surveying is limited to asset
inventory (e.g. presence, location, asset dimensions, using LiDAR surveying techniques), all other inspections (safety,
condition etc.) are carried out manually.
Did the organization identify a data owner for each asset data
group?
☒ Yes
☐ No
Optional additional comments:
Regarding Asset Data sharing:
a) Which Entities can be considered as the main organization’s stakeholders for
information exchange regarding managed transportation network?
☒ Government
☐ Other Transportation Company (same managed network
type)
☐ Regional / Local Authorities
☐ Other Transportation Company (different managed
network type)
☒ Other
If Other please specify: Service providers working for Highways England under contract.
b) Which key datasets does the organization disseminate? Please indicate, if present, the relevant ones for
multimodality purposes.
[Free Text]
ASSET DATA CLASSIFICATION
Regarding asset inventory, please indicate, choosing from the following,
the key asset categories managed through IT Systems
Main Category Sub Category
☒ Carriageway ☒ Flexible Pavement
☒ Flexible composite pavement
☒ Rigid Concrete Pavement
☒ Rigid Composite Pavement
☒ Road Markings
☒ Road Stud
☐ Other, please specify: ______________
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 69 / 82
☒ Kerbs
☒ Structure ☒ Bridge
☒ Tunnel
☒ Underpass
☒ Retaining Wall
☒ Culvert
☒ Drainage
☒ Viaduct
☐ Other, please specify: ______________
☒ Lighting ☒ Lighting Column
☒ High mast lighting
☒ Lighting unit attached to wall/pole
☐ Other, please specify: __________________
☒ Road Furniture ☒ Road Sign
☒ Safety Barrier
☒ Noise Barrier
☒ Safety Barrier
☒ Pedestrian Barrier
☒ Billboard
☒ Verge Marker Post
☐ Bus Shelter
☒ Toll Station
☒ Sign Gantry
☒ Gate
☐Other, please specify: _____________
☒ Equipment ☒ Traffic Camera/Sensor
☒ Weather Station
☒ VMS
☒ Ventilation System
☒ Traffic Signal
☒ SOS Pillar
☒ Fire Fighting System
☐ Wi-Fi System
☐Other, please specify: _____________
SURVEY REPLY BY TRANSPORT INFRASTRUCTURE OF IRELAND
GENERAL CONTEXT
What kind of transport infrastructure network does the
organization manage? What is its extension?
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 70 / 82
Type Extension (#km) Sub category
X Road 5306 km (motorways = 916km, Dual Carriageways = 294 km
Single Carriageway 4,096)
X Rail 36.5 km Light Rail Network
☐ Air
☐ Water
☐ Other (please specify)
What is the responsibility related to assets?
X Ownership
X Concession
Optional additional comments:
Transport Infrastructure Ireland responsible for the national road network and the Light Rail Network, further information
on how the road network is managed available here
Which are the processes related to asset management for whom the
organization is responsible for?
X Design
X Build
X Maintain
X Enhance
X Operate
Optional additional comments:
Concerning asset management framework:
g) At which stage can be considered the development of strategies, objectives, policies
or procedures related to Asset Management:
☐ Initial
X On course preliminary
☐ On course advanced
☐ Completed
h) Which standards have been considered to design the model?
☐ ISO 55000
☐ PAS 1192
☐ ISO/TS 8000
X PAS 55
☐ BS 1192
☐ Other
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 71 / 82
If Other, please specify: _________________________
i) Describe briefly the contents of current AM framework adopted by the organization:
Not Applicable
ASSET INFORMATION MODEL
Which are the asset information domains covered by IT Systems?
Main Domain Sub Domain
☐ Legal ☐ Asset related contractual information
☐ Risk assessment and control measures
☐ Safety/Environmental information
☐ Other, please specify: __________________
☐ Financial ☐ Construction Costs
☐ Purchase/Leasing costs
☐ Maintenance/Operating costs
☐ Asset replacement value
☐ Downtime impact
☐ Whole life / Historical cost
☐ Other, please specify: __________________
X Technical X Engineering data
X Operational Data (e.g. technical performance characteristics, design limits)
☐ Details of Asset Dependencies and interdependencies
X Design parameters
☐ Commissioning Data
☐ Other, please specify: __________________
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 72 / 82
X Managerial ☐ Asset identification numbers
X Asset location (e.g. spatial referencing, geographical information systems)
X Warranties and guarantee periods
X Maintenance and inspection data
X Emergency Plan
X Work schedules
X☐ Asset related standards, processes and procedures
X Details of historical asset failures, causes and consequences
☐ Other, please specify: __________________
☐ Commercial ☐ Condition and performance targets/standards
☐ Utilization Data
☐ KPI
☐ Level of Services
☐ Other, please specify: __________________
For the information managed through IT Systems, please rate the
completeness of collected data compared to the entire transportation network:
Domain Level of completeness (1 high to 5 low)
Legal ☐ 1 ☐ 2 ☐ 3 X 4 ☐ 5
Financial ☐ 1 ☐ 2 ☐ 3 X 4 ☐ 5
Technical ☐ 1 X 2 ☐ 3 ☐ 4 ☐ 5
Managerial ☐ 1 X 2 ☐ 3 ☐ 4 ☐ 5
Commercial ☐ 1 ☐ 2 X 3 ☐ 4 ☐ 5
What are the implemented IT systems that support asset information
management?
☐ Work Programme Planning and scheduling systems ☐ Materials management and spares inventory systems
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 73 / 82
X Document Management Systems
☐ Purchasing Systems
☐ Maintenance Systems
☐ Property Systems
☐ Accounting and financial planning systems
☐ Engineering design and modelling systems
☐ Performance reporting systems
X Condition monitoring systems
☐ Traffic Management Systems
☐ Knowledge management systems
☐ Other, please specify: GIS
Concerning the presence of a Common Data Environment (CDE -Single
Source of Information for any given asset, used to collect, manage and dissiminate all
relevant approved files, documents, and data for multi-disciplinary teams in a managed
process), please define:
g) At which stage is the overall process of implementation of CDE?
X Initial
☐ On course preliminary
☐ On course advanced
☐ Completed
h) Which information domains, does the implemented CDE contain? In case not
implemented yet, please indicate the integration targets:
☐ Legal
☐ Financial
☐ Technical
X Managerial
☐ Institutional
☐ Other
If Other, please specify: _________________________
i) Which Asset Management decision processes the CDE currently supports?
☐ Project Selection ☐ Budgeting
☐ Strategic Investments ☐ Performance evaluation and monitoring
X Reporting and External Communication ☐ Other
If Other, please specify: _________________________
Did the organisation develop an Asset Data Dictionary in order to deploy
a common language regarding infrastructure’s assets?
☐ Yes X No
Optional additional comments:
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 74 / 82
Which is the strategy adopted by the organization to perform a
reliable data integration between several data sources? Has a Master Data Management
methodology been applied?
No
ASSET DATA MANAGEMENT
Regarding asset data management procedures, please define:
a) Which formal procedures has the organization implemented?
X Data Collection and Maintenance
☐ Data Storage and Retrieval
☐ Other
If Other, please specify: _________________________
☐ Data Sharing and Exchange
☐ Data Quality
Optional additional comments:
b) For Data Quality assurance/control, which solutions have been implemented?
☐ Periodical Analysis/Audit
☐ Use of Automatic procedures
☐ Third Party Software solutions
☐ Other
If Other please specify:________________________
c) For Data collection, which roadway asset types are involved? Which is the adopted
method to perform the activity? (in case of different transportation network, please
integrate/modify the asset types)
Asset Type Data collection method
X Pavements X Automatic
☐ Manual
☐ Both
X Structure (e.g. Bridges, Tunnels, Underpass, etc.) ☐ Automatic
X Manual
☐ Both
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 75 / 82
X Equipment (VMS, traffic camera, etc.) ☐ Automatic
X Manual
☐ Both
X Other Items (e.g. road signs, safety barriers, etc.) ☐ Automatic
X Manual
☐ Both
Optional additional comments:
Did the organization identify a data owner for each asset data
group?
☐ Yes
X No
Optional additional comments:
Regarding Asset Data sharing:
a) Which Entities can be considered as the main organization’s stakeholders for
information exchange regarding managed transportation network?
X Government
☐ Other Transportation Company (same managed network
type)
X Regional / Local Authorities
☐ Other Transportation Company (different managed
network type)
☐ Other
If Other please specify:________________________
b) Which key datasets does the organization disseminate? Please indicate, if present, the relevant ones for
multimodality purposes.
TII has recently engaged in the Open Data initiative around the provision of data held by the organisation to the public via
http://data.tii.ie/
ASSET DATA CLASSIFICATION
Regarding asset inventory, please indicate, choosing from the following,
the key asset categories managed through IT Systems
Main Category Sub Category
X Carriageway X Flexible Pavement
X Flexible composite pavement
X Road Markings
X Road Stud
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 76 / 82
☐ Rigid Concrete Pavement
☐ Rigid Composite Pavement
☐ Kerbs
☐ Other, please specify: ______________
X Structure X Bridge
X Tunnel
X Underpass
X Retaining Wall
X Culvert
Drainage
X Viaduct
☐ Other, please specify: ______________
X Lighting X Lighting Column
X High mast lighting
X Lighting unit attached to wall/pole
☐ Other, please specify: __________________
X Road Furniture X Road Sign
X Safety Barrier
X Noise Barrier
X Safety Barrier
☐ Pedestrian Barrier
☐ Billboard
X Verge Marker Post
☐ Bus Shelter
X Toll Station
X Sign Gantry
☐ Gate
☐Other, please specify: _____________
X Equipment X Traffic Camera/Sensor
X Weather Station
X VMS
☐ Ventilation System
☐ Traffic Signal
☐ SOS Pillar
☐ Fire Fighting System
☐ Wi-Fi System
☐Other, please specify: _____________
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 77 / 82
SURVEY REPLY BY ANAS
GENERAL CONTEXT
What kind of transport infrastructure network does the
organization manage? What is its extension?
Type Extension (#km) Sub category
☒ Road 25.000 KM (e.g. toll motorways, highways, urban roads,
national roads, etc.)
☐ Rail
☐ Air
☐ Water
☐ Other (please specify)
What is the responsibility related to assets?
☐ Ownership
☒ Concession
Optional additional comments:
Which are the processes related to asset management for whom the
organization is responsible for?
☒ Design
☒ Build
☒ Maintain
☒ Enhance
☒ Operate
Optional additional comments:
Concerning asset management framework:
j) At which stage can be considered the development of strategies, objectives, policies
or procedures related to Asset Management:
☐ Initial
☒ On course preliminary
☐ On course advanced
☐ Completed
k) Which standards have been considered to design the model?
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 78 / 82
☐ ISO 55000
☐ PAS 1192
☐ ISO/TS 8000
☐ PAS 55
☐ BS 1192
☐ Other
If Other, please specify: _________________________
l) Describe briefly the contents of current AM framework adopted by the organization:
[Free Text]
ASSET INFORMATION MODEL
Which are the asset information domains covered by IT Systems?
Main Domain Sub Domain
☒ Legal ☐ Asset related contractual information
☐ Risk assessment and control measures
☐ Safety/Environmental information
☐ Other, please specify: __________________
☒ Financial ☒ Construction Costs
☒ Purchase/Leasing costs
☒ Maintenance/Operating costs
☐ Asset replacement value
☐ Downtime impact
☐ Whole life / Historical cost
☐ Other, please specify: __________________
☒ Technical ☒ Engineering data
☒ Operational Data (e.g. technical performance characteristics, design limits)
☐ Details of Asset Dependencies and interdependencies
☒ Design parameters
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 79 / 82
☒ Commissioning Data
☐ Other, please specify: __________________
☒ Managerial ☒ Asset identification numbers
☒ Asset location (e.g. spatial referencing, geographical information systems)
☐ Warranties and guarantee periods
☒ Maintenance and inspection data
☐ Emergency Plan
☒ Work schedules
☒ Asset related standards, processes and procedures
☐ Details of historical asset failures, causes and consequences
☐ Other, please specify: __________________
☒ Commercial ☒ Condition and performance targets/standards
☐ Utilization Data
☐ KPI
☒ Level of Services
☐ Other, please specify: __________________
For the information managed through IT Systems, please rate the
completeness of collected data compared to the entire transportation network:
Domain Level of completeness (1 high to 5 low)
Legal ☒ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5
Financial ☐ 1 ☐ 2 ☐ 3 ☒ 4 ☐ 5
Technical ☐ 1 ☐ 2 ☒ 3 ☐ 4 ☐ 5
Managerial ☐ 1 ☐ 2 ☐ 3 ☒ 4 ☐ 5
Commercial ☐ 1 ☒ 2 ☐ 3 ☐ 4 ☐ 5
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 80 / 82
What are the implemented IT systems that support asset information
management?
☒ Work Programme Planning and scheduling systems
☒ Document Management Systems
☒ Purchasing Systems
☒ Maintenance Systems
☒ Property Systems
☒ Accounting and financial planning systems
☐ Materials management and spares inventory systems
☐ Engineering design and modelling systems
☒ Performance reporting systems
☐ Condition monitoring systems
☒ Traffic Management Systems
☐ Knowledge management systems
☐ Other, please specify: ___________________
Concerning the presence of a Common Data Environment (CDE -Single
Source of Information for any given asset, used to collect, manage and dissiminate all
relevant approved files, documents, and data for multi-disciplinary teams in a managed
process), please define:
j) At which stage is the overall process of implementation of CDE?
☒ Initial
☐ On course preliminary
☐ On course advanced
☐ Completed
k) Which information domains, does the implemented CDE contain? In case not
implemented yet, please indicate the integration targets:
☐ Legal
☒ Financial
☒ Technical
☒ Managerial
☒ Institutional
☐ Other
If Other, please specify: _________________________
l) Which Asset Management decision processes the CDE currently supports?
☐ Project Selection ☐ Budgeting
☐ Strategic Investments ☐ Performance evaluation and monitoring
☐ Reporting and External Communication ☐ Other
If Other, please specify: _________________________
Did the organisation develop an Asset Data Dictionary in order to deploy
a common language regarding infrastructure’s assets?
☐ Yes ☒ No
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 81 / 82
Optional additional comments:
Which is the strategy adopted by the organization to perform a
reliable data integration between several data sources? Has a Master Data Management
methodology been applied?
ASSET DATA MANAGEMENT
Regarding asset data management procedures, please define:
a) Which formal procedures has the organization implemented?
☒ Data Collection and Maintenance
☐ Data Storage and Retrieval
☐ Other
If Other, please specify: _________________________
☐ Data Sharing and Exchange
☐ Data Quality
Optional additional comments:
b) For Data Quality assurance/control, which solutions have been implemented?
☐ Periodical Analysis/Audit
☐ Use of Automatic procedures
☐ Third Party Software solutions
☐ Other
If Other please specify:________________________
c) For Data collection, which roadway asset types are involved? Which is the adopted
method to perform the activity? (in case of different transportation network, please
integrate/modify the asset types)
Asset Type Data collection method
☒ Pavements ☐ Automatic
☐ Manual
☒ Both
☒ Structure (e.g. Bridges, Tunnels, Underpass, etc.) ☐ Automatic
☒ Manual
☐ Both
☒ Equipment (VMS, traffic camera, etc.) ☐ Automatic
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 82 / 82
☐ Manual
☒ Both
☒ Other Items (e.g. road signs, safety barriers, etc.) ☐ Automatic
☒ Manual
☐ Both
Optional additional comments:
Did the organization identify a data owner for each asset data
group?
☒ Yes
☐ No
Optional additional comments:
Regarding Asset Data sharing:
a) Which Entities can be considered as the main organization’s stakeholders for
information exchange regarding managed transportation network?
☒ Government
☒ Other Transportation Company (same managed network
type)
☒ Regional / Local Authorities
☐ Other Transportation Company (different managed
network type)
☐ Other
If Other please specify:________________________
b) Which key datasets does the organization disseminate? Please indicate, if present, the relevant ones for
multimodality purposes.
[Free Text]
ASSET DATA CLASSIFICATION
Regarding asset inventory, please indicate, choosing from the following,
the key asset categories managed through IT Systems
Main Category Sub Category
☒ Carriageway ☒ Flexible Pavement
☒ Flexible composite pavement
☒ Road Markings
☐ Road Stud
AM4INFRA – 713793 Public (PU) D3.1 – Asset Data Dictionary
Page 83 / 82
☒ Rigid Concrete Pavement
☒ Rigid Composite Pavement
☐ Kerbs
☐ Other, please specify: ______________
☒ Structure ☒ Bridge
☒ Tunnel
☒ Underpass
☒ Retaining Wall
☒ Culvert
☒ Drainage
☒ Viaduct
☐ Other, please specify: ______________
☒ Lighting ☒ Lighting Column
☐ High mast lighting
☐ Lighting unit attached to wall/pole
☐ Other, please specify: __________________
☒ Road Furniture ☒ Road Sign
☒ Safety Barrier
☒ Noise Barrier
☒ Safety Barrier
☒ Pedestrian Barrier
☐ Billboard
☐ Verge Marker Post
☐ Bus Shelter
☐ Toll Station
☐ Sign Gantry
☐ Gate
☐Other, please specify: _____________
☒ Equipment ☒ Traffic Camera/Sensor
☒ Weather Station
☒ VMS
☒ Ventilation System
☐ Traffic Signal
☒ SOS Pillar
☐ Fire Fighting System
☐ Wi-Fi System
☐Other, please specify: _____________