Road Management Data Standard V2
Road Management Data Standard V2
AP-T334-18
Prepared by Publisher
Asset management, data schema, data sharing, data specification, • Department of Planning, Transport and Infrastructure South
Australia
data standard, road investment, road management
• Department of State Growth Tasmania
• Department of Infrastructure, Planning and Logistics
ISBN 978-1-925671-62-9 Northern Territory
• Transport Canberra and City Services Directorate,
Austroads Project No. ASP2112 Australian Capital Territory
Austroads Publication No. AP-T334-18 • The Department of Infrastructure, Regional Development
and Cities
Publication date June 2018
• Australian Local Government Association
Pages 254
• New Zealand Transport Agency.
© Austroads 2018
This work is copyright. Apart from any use as permitted under the Copyright Act 1968, no part may be reproduced by any process without
the prior written permission of Austroads.
Acknowledgements
Opus International Consultants (Opus) developed and produced this Standard, with the assistance of GISSA International (GISSA) and
representative industry stakeholders, on behalf of Austroads.
The basis for the inventory ‘as constructed’ data standards has been adopted from R-Spec V3C, which has evolved from initial work
undertaken in Australia and more recently in New Zealand by the Transport Analytics Governance Group (TAGG). Austroads
acknowledges this contribution and the role that GISSA had in facilitating and producing these previous Standards.
The basis for the classification data standards has been adopted from the ‘One Network Road Classification’ system developed by The
Road Efficiency Group in New Zealand.
This report has been prepared for Austroads as part of its work to promote improved Australian and New Zealand transport outcomes by
providing expert technical input on road and road transport issues.
Individual road agencies will determine their response to this report following consideration of their legislative or administrative
arrangements, available funding, as well as local circumstances and priorities.
Austroads believes this publication to be correct at the time of printing and does not accept responsibility for any consequences arising from
the use of information herein. Readers should rely on their own skill and judgement to apply information to particular issues.
Data Standard for Road Management and Investment in Australia and New Zealand Version 2
Summary
This Data Standard for Road Management and Investment in Australia and New Zealand (the Standard) has
been developed in response to a need to standardise and harmonise data sets that support common road
management and investment activities. Specifically, this Standard establishes a common understanding of
the meaning or semantics of the data, to ensure correct and proper use and interpretation of the data by its
stakeholders. The data specifications are specific to the data that is typically and routinely used for road
management and investment purposes. It provides consistency in data definition and format. The Standard
will assist with road management and investment activities including: asset and service performance
assessment, performance benchmarking, road research, policy development, expenditure comparisons,
funding approvals, supporting national reforms, national reporting, innovation, shared services, and inter-
organisation communications.
This Standard has been developed to support asset information management systems for data collection,
finance, risk, and information. It is the product of comprehensive consultation in Australia and New Zealand
across the road industry.
This version (Version 2) of the Standard highlights an initial Priority Harmonisation Subset (PHS) of data, that
will be the subject of further review and stakeholder consultation. The PHS and wider Standard will continue
to develop and mature in consultation with stakeholders and in support of national reforms.
The Standard allows organisations to determine their desired level of sophistication with respect to both
asset inventory recording and asset management planning and provides the relevant data specification in
this regard. This approach is consistent with the fundamental principles of ISO 55000:2014 Management
System – Asset Management, particularly regarding maximising ‘value’ from assets.
In this Standard the New Zealand One Network Road Classification (ONRC) has been used as an example
of a classification system. This classification has not been endorsed as the primary functional classification
system in Australia. The outcomes of discussions on functional road classification in the context of national
reforms will inform future versions of a Data Standard for Road Management and Investment.
An internal Strategic Business Case report was prepared for Austroads in early 2015, which drew the
conclusion that development of road asset data standards would support the following:
a platform to improve road agency practices and drive innovation; and
The Standards presented in this document have been developed in response to item (b) outlined above.
Evaluation of the cost and benefits of establishing road data standards, suggests that benefits can be largely
achieved by seeking harmonisation of key subsets of data as an embedded element of national reforms,
while making a wider set of standards available as a practice guide to road managers and the industry sector
that supports road asset management activities.
The potential benefits of this kind of targeted approach to harmonisation of road related data include:
• Efficiency of maintenance activities and spending
• Ability to deliver heavy vehicle road reform benefits
• Improved net benefit from capacity expansion activities
• Lower data collection costs
• Lower operational costs
• Improved ability to leverage new technologies
Contents
Summary ............................................................................................................................................................ i
1. Overview .................................................................................................................................................... 1
1.1 Purpose............................................................................................................................................. 1
1.2 Data Scope ....................................................................................................................................... 1
1.3 Data Standard Context ..................................................................................................................... 2
1.4 Benefits and Impacts ........................................................................................................................ 3
1.5 Reporting Data in terms of this Standard ......................................................................................... 3
1.6 Prioritised Harmonised Set ............................................................................................................... 3
2. Road Management and Investment Practice ......................................................................................... 5
3. Function Groups and Data Items ............................................................................................................ 8
3.1 Data Specification Structure ............................................................................................................. 8
3.2 Function Groups ............................................................................................................................... 9
Function Group Scope ......................................................................................................... 9
Asset Lifecycle and Function Groups ................................................................................ 12
Function Group Relationships ........................................................................................... 15
4. Setting the Context ................................................................................................................................. 17
4.1 Using This Standard ....................................................................................................................... 17
4.2 Road Network Definition ................................................................................................................. 17
Road Network Topology .................................................................................................... 17
Link Sections ...................................................................................................................... 19
Relative Lengths ................................................................................................................ 20
4.3 Location Referencing System ......................................................................................................... 21
4.4 Asset Planning ................................................................................................................................ 21
4.5 Asset Data ...................................................................................................................................... 23
4.6 Data Schemas ................................................................................................................................ 24
Function Groups ................................................................................................................ 24
Data Items .......................................................................................................................... 25
Asset Management and Investment Activities ................................................................... 25
Logical Navigation to Data Specifications.......................................................................... 26
4.7 Determining the Appropriate Levels of Sophistication .................................................................... 26
5. Asset Data Life Cycle ............................................................................................................................. 29
6. Data Classes ............................................................................................................................................ 31
6.1 Data Class Definition ...................................................................................................................... 31
6.2 Data Class Attributes (Data Item) ................................................................................................... 31
7. Data Item Specifications (Common Classes) ....................................................................................... 34
7.1 Object Locations ............................................................................................................................. 34
Points ................................................................................................................................. 35
Polylines ............................................................................................................................. 36
Polygons ............................................................................................................................ 38
7.2 Data Control .................................................................................................................................... 41
Tables
Figures
1. Overview
1.1 Purpose
This Standard has been developed to provide a common understanding and language for the management
and investment in road and associated infrastructure in Australia and New Zealand. It is intended to be
utilised by all road asset owners, managers, road network funding agencies, stakeholders and service
providers in the planning, delivery, operation, maintenance, disposal and reporting of asset management
functions across the road asset portfolio.
• Organisations involved in provision of funding and investment to road asset owners and organisations
monitoring road network performance, in the context of structure and content of reports and submissions
requested from road asset portfolio owners and managers;
• Contractors, service providers or project developers that perform asset management related services for
road organisations including their suppliers involved in defining, designing, implementing,
commissioning and integrating new or altered assets into the operating network; and
• Software vendors involved in developing, structuring and/or configuring asset management information
systems/software solutions.
This Standard presents data specifications that are technology and software agnostic in that they are
intended to be used by anything and anyone.
This Standard does not specify data collection or storage requirements, nor does it provide guidance on how
to create an asset register.
This Standard provides structure regarding common data sets to manage assets. It also includes a more
extensive data set for organisations operating at higher levels of sophistication in asset management practice.
These benefits have been determined though an Investment Logic Mapping (ILM) workshop and subsequent
review sessions with the Austroads Asset Task Force (Austroads ATF):
• Improved reform outcomes for heavy vehicle and road pricing and investment;
• More productive design, construction, maintenance and operation of the roads network;
• Better justification and monitoring of investment in roads; and
• Wider benefits to the community resulting from road data being more accessible for the purposes of
information technology, health, and the environment.
Achieving these benefits will generate the following road industry-wide impacts:
• Common basis for data Exchange between stakeholders;
• Common basis for data used in national data analytics;
• Common basis for software and data analytics; and
• Base data set to support International Standard ISO 55001: Management System – Asset Management.
• Management [M] – A list of data items that represent the minimum data set for effective asset and
maintenance management. This Standard recommends that Road Agencies adopt this management set
of data items as a priority for implementation.
Data items that feature in the minimum management data set have been identified in the relevant data
definition tables with a ‘M’ notation in the PHS data class attribute.
Additional categories of PHS will be developed in the future to further aid in the adoption and implementation
of this Standard.
The asset management objectives are delivered by the organisations Asset Management System (AMS),
which as defined in ISO 55000 is an integrated management system including people, processes, and
technology. Data in the context of an AMS, sits under technology and is typically managed using computer
software such as an Asset Information Management System (AIMS) or Computerised Maintenance
Management System (CMMS). While the AMS focusses on a planned ‘whole of life’ approach to managing
assets, there is a direct interface to asset development as shown in Figure 2.1. Asset development in this
context is a form of asset acquisition, which provides opportunity to incorporate and benefit from asset
management considerations.
The optimisation of the ‘whole of life’ asset management cycle is considered in four phases (planning,
acquisition, operations, and disposal) as shown in Figure 2.1.
This is the typical process for managing assets from ‘conception to disposal’, including all the asset
management activities required to manage an asset portfolio to ensure the required level of service is
delivered sustainably in terms of risk, cost, and performance.
Asset management requires effective integration of many key elements supported and coordinated across
different disciplines. The International Infrastructure Management Manual (2015) describes asset
management as “the combination of management, financial, economic, engineering, and other practices
applied to physical assets with the objective of providing the required level of service in the most cost
effective manner.” The prime objective is to deliver defined outcomes from infrastructure assets that add
value to the organisation and its customers. Value can be defined in different ways depending upon the
asset outcomes required. Typical outcomes from asset management include minimising cost of assets,
minimising asset risk, and maximising customer experience.
The asset management investment planning process includes the identification for asset acquisition, which
may require new assets created through a design and construction delivery process. New assets, whether
constructed or acquired, are incorporated into the existing asset portfolio and managed in conjunction with
the existing portfolio of assets.
Planning
The asset management objectives define the outcomes that are required from the assets in terms of both
asset and service performance. Organisations that focus on asset services tend to configure the asset
management system on strategic long-term planning that maximises the value of assets. A focus on assets
typically drives an asset preservation based planning strategy, which needs to be effectively balanced with
the demand driven asset development focussed planning strategy.
The asset management objectives will determine the asset management outputs including the asset and
service performance requirements. This planning phase explores the options available to the organisation
including non-asset solutions to deliver the defined asset management objectives. Asset planning is typically
performed in three broad types: strategic planning; tactical planning; and operational planning.
The strategic planning process is essentially at the heart of asset management where informed decisions are
made for the future based upon an understanding of the required asset outcomes (or levels of service),
future asset and service performance, asset related risk, and the cost to achieve the required asset outputs.
Acquisition
The tactics for creating or renewing an asset. This phase explores options such as new construction,
inheriting an existing asset, improving an existing asset, buying a new asset, or outsourcing the asset related
services. Project justification analysis, such as a benefit to cost ratio and a triple bottom line approach are
typically used to determine the best option for the organisation and its stakeholders. It is important to
consider the ongoing cost of operations, maintenance and renewal in any analysis when comparing options
over the same time period.
Operations
Asset preservation practice is shifting from short-term reactive maintenance activities, to proactive long-term
planned asset preservation strategies and related routine and periodic maintenance activities. This practice
requires clearly defined levels of service and related physical works intervention criteria, which determine the
triggers for action. Supporting tasks include appropriate asset condition monitoring programs followed by
data analysis for understanding condition and performance.
Disposal
Asset disposal occurs when the asset becomes redundant in its current form or function. Either the service is
no longer needed, the current assets can no longer provide the service capacity, or technological advances
have created a more cost effective alternative asset. In some cases, the new asset solution may incorporate
the current asset in full or part.
Design
The key consideration in the design process is to understand the required level of service. This is typically
captured in the form of design criteria that provide the desired outcome from the asset. Given that the asset
will be inherited into the asset management system, it is also good practice to undertake an asset
management design review, where the ongoing operational, maintenance, and renewal costs are assessed
and potentially ‘designed out’ or ‘reduced’. This phase aims to maximise the effectiveness of the designed
asset.
Construction
The longevity of the asset is determined by the quality of materials and the general quality of construction.
Accordingly, the construction quality management process becomes very important to maximising the useful
life of the asset. A key asset management consideration during construction is the transfer of as-built asset
data into the asset owners Asset Information Management System.
This Standard is primarily structured into function groups. The inventory, and to a limited extent, the condition
function group are further broken down by asset groups. Refer Figure 3.1.
In terms of the data specifications, data Items are represented in rows and the Metadata Elements are
represented by the columns, as shown in Figure 3.2.
This Standard defines the data requirements for a road Asset Information Management System (AIMS) and
for reporting, to support activities for road management and investment purposes. The function groups are
described in Table 3.1.
Asset data items presented in this Standard cover the whole-of-life management of assets required to
support and substantiate decisions made over the life cycle. These decisions include but are not limited to
the following:
• Investment management requirements including asset capitalisation and ‘whole-of-life’ costs;
• Asset handover requirements including asset acceptance information; and
• Asset configuration change requirements including asset approvals or sub-component approvals, new
assets, configuration and operational changes including changes in asset strategy and concessions to
Standards.
A vertically integrated Asset Management System (AMS) creates a framework for effective asset
management practice by directly linking the operational activities to the delivery of the asset management
objectives. This linkage is sometimes referred to as ‘the golden thread’ or ‘line of sight’ in a business context.
This AMS allows asset management objectives and outcomes to be understood, asset services to be
monitored, readily shared asset related information, and promotes informed decision making.
The following Figure 3.3 relates the function groups to the typical three levels of asset management planning
activity within an organisation:
Strategy The asset and service outcomes that deliver on the organisation’s asset management
objectives including organisational wide asset portfolio management and investment activities.
Strategy has a long-term focus (ie. 10 years plus). The data requirements that support
strategic asset planning and reporting include data items primarily pertaining to classification,
inventory, condition, performance, and demand.
Tactics The tactical activities that manage the assets and related services to deliver the required asset
management objectives. This includes evidence based decision making for developing the
forward works program for each asset group. Tactics have a medium-term focus (ie. up to 6
years). The data requirements that support tactical asset planning and reporting include data
items primarily pertaining to network, classification, inventory, condition, performance,
demand, and works & costs.
Operations The transactional activities that operate and maintain the assets. This includes data collection,
road network operational activities, routine maintenance, periodic maintenance, asset
renewals/replacements/refurbishments, and new assets. Operations have a short-term focus
(ie. 1 to 3 years). The data requirements that support operational asset planning and reporting
are contained under all the functional groups provided in this Standard.
Figure 3.4 presents the typical asset management and asset development activities and their related function
groups.
The purpose for the data is dependent upon the Asset Management (AM) phase as shown in Table 3.2.
This Standard has been specifically developed for broad use regardless of the asset management phase.
Some of the function groups presented in this Standard are inter-related, where data is exchanged between
related function groups. These relationships have been mapped and presented in Figure 3.5.
The key steps to using this Standard are shown in Figure 4.1.
This Standard allows for various levels of sophistication for collecting, managing, and using inventory data,
and asset location referencing. The lowest level of asset location referencing uses the road centreline as the
principle reference point. Accordingly, this referencing method requires the road network to be defined and
geospatially represented as road centreline nodes and links.
This section provides information regarding the lowest common method for achieving a network
centreline model. Organisations may use a more sophisticated topology model that better represents
its road network, however the principles presented here are likely to still apply. The guidance
provided in this section is not intended to be read as a specification.
It is recognised that some organisations create and use static sectioning for their business process and
reporting. This type of sectioning generally represents multiple attributes within the one section, however
when the attribute criteria changes, it necessitates a change in the network section. By its nature, this
approach results in changes to the network model, because it utilises aggregation of these sections to derive
a network model.
The preferred approach is to divide the individual attributes that are defined within a static section and create
an individual layer for this data. For example, if in the past link sections have been created based on
pavement type, traffic volume, pavement width and speed, then individual layers for the individual dataset
would be created. In this case separate layers would be created for pavement type, traffic volume, pavement
width and speed. The benefit of this approach is that it enables the network model to be dynamically
segmented using any individual, or combined data sets.
Link In a road network, portion of a road (single links) between two junctions or interchanges or
intersections. Its basic characteristics are length, vehicle speeds, travel times, and number of lanes.
Figure 4.2 and Figure 4.3 illustrate the node and link representation.
Figure 4.3: Road Network Definition Model – Example Nodes and Links Representation
Link Sections
A road link is typically a section of road with homogenous features such as traffic and loading volumes,
pavement type (sealed, unsealed, structural, bridge), width, number of lanes and urban/rural classification
along its length. This section does not specify the criteria for defining or creating link sections, however does
provide practical guidance.
Link sections can be either static or be dynamically determined based upon the criteria applied. Dynamic link
sections are more likely to feature in the future as the availability of data expands and the purpose for the link
is refined.
A road may be broken down into multiple link sections if any of the following criteria change along its length
such as:
• A change in the number of lanes, i.e. from 2 to 3 (at the start of a passing lane).
• The speed limit changes to greater than 70km/hr (urban to rural).
• The width changes by more than 2.5m over a significant length (typically >100m).
• Traffic volumes and/or composition change significantly such as at major intersections.
• The road changes in surface type i.e. sealed to unsealed, thin surface flexible to bridge.
Link section data includes dimension and road section characteristics and provides the principal framework
for all road corridor assets to be attached to. Link breaks define the start or end of each link section.
Road length is an aggregation of the link sections for that road. However, there are different groups of links
that need to be considered.
Relative Lengths
This Standard consistently applies a common principle for the relative relationship between roads, link
sections, and assets. Basic rules for defining the length of these entities, in terms of link sections are:
Road Link Length The aggregated length of the link sections along the same road.
Link Section Length A section of road that represents homogeneous features such as the road surface
width or road classification.
Asset Length The measured length of physical assets that are attached to roads and link
sections such as retaining walls, road pavement, and footpaths. Note that asset
lengths do not need to be contained within an individual link section length,
provided the Asset Information Management System is configured to allow asset
registration against contiguous lengths of link sections along a road.
The following Figure 4.5 provides a visual representation of these three entities:
Organisations are encouraged to maintain their existing location referencing systems regardless of whether
this system is deemed to exceed the minimum required level of sophistication. Spatial referencing is likely to
be universally used by all stakeholders in the future and is already the basis for location referencing for
existing ‘as-constructed’ data capture processes (e.g. R-Spec and ADAC).
For many organisations, the current planning process is a symptom of past practice and may not represent
desired practice. Maturity in the planning process evolves over time, typically in response to delivering
organisational objectives and improvements in planning capability. Other determinates include resources,
capabilities, technology, and the budget approval processes.
It is recognised that road agencies operate at different levels of sophistication for asset planning, which can
broadly be grouped into three categories. Each level of sophistication incrementally requires more detailed
data to inform the decision process. All three planning practices have been incorporated into this Standard
(Figure 4.7):
An asset planning maturity matrix is shown in Figure 4.8, which was developed, in conjunction with
stakeholder organisations, to identify the potential outcome from evolving asset management practices. This
figure shows how an organisation can evolve from simply reacting to asset defects (maintenance delivery) to
developing a planned approach for delivering asset service outcomes that link to the organisations objectives
(A to B).
This matrix includes both function group, as it relates to asset lifecycle, and level of data application in terms
of operations, tactics, and strategy (including organisational level reporting).
As a guiding principle data, should be collected which is sufficient but no more than is necessary to
implement the business requirements of the organisation. The business requirement would include reporting.
In some instances, this might require collecting only Network level data (D1) and in other instances
component level data (D3).
Function Groups
This Standard has structured asset data tables under fourteen function groups that collectively support
common activities across road management and investment responsibilities. Accordingly, the data items
within each function group has been developed by considering their:
• Meaningful purpose and use with the function group;
• Integration with other function groups to support inter-operability; and
• Context relative to other data items.
As described in Section 3.2 and detailed in Section 8, this Standard is structured around the following
function groups:
1. Network
2. Classification
3. Inventory
4. Condition
5. Demand
6. Utilisation
7. Criticality
8. Risk
9. Resilience
10. Performance (Asset)
11. Performance (Financial)
12. Performance (Service)
13. Access
14. Works and Costs
Data Items
To assist information management and data specialists will a quick reference guide, Appendix A captures all
the individual data items in alpha numeric order. This approach allows efficient identification of individual
data items, as an alternative means to navigation of this Standard.
To ensure completeness and integration of the data items across the various function groups, asset
management and investment activities have been defined. This approach has identified the core business
activities that occur within road agencies and allows the data requirements to be clearly identified.
Furthermore, this approach allows an alternative means to navigate this Standard where an asset
management and investment activity becomes the starting point for locating data specification details.
Appendix B uses a matrix structure to map the function groups detailed in Section 8 against the following
core road management and investment activities:
• Network definition;
• Information management;
• Corridor Management;
• Maintenance management;
• Road safety management;
• Asset financial management;
• Asset management data analytics, modelling, planning, and optimisation;
• Asset Management System (ISO 55001: Management System for Managing Assets);
• Asset reporting and communication; and
• Asset and project development.
As shown in Figure 4.10, this Standard has been structured to allow the user to locate desired data items via
the three different navigation methods as follows:
• Function Groups;
• Data items; and
• Activities.
Data Items Appendix B contains a listing of the unique data items regarding the related function
groups and asset groups where applicable.
Activities Appendix C contains a listing of road management and investment activities with a
reference to related function groups.
Not all data items detailed in this Specification will be applicable to all organisations. To assist with
determining which data items are considered applicable to an organisation. This section provides guidance
to assess an appropriate level of sophistication, in terms of:
• ‘L’ - Location Referencing (Section 4.3);
• ‘P’ - Asset Planning (Section 4.4); and
• ‘D’ - Asset Data (Section 4.5).
The data items in the Standard have been categorised into one of the above three categories, as recorded in
the ‘Purpose’ metadata element field, and then assessed against the sophistication definitions in Sections
4.3, 4.4 and 4.5. That is, each individual data item is notionally identified as being required to meet
sophistication level 1, 2 or 3 under one of the above three categories. This approach allows an organisation
to broadly target the data items that are generally applicable to the level of sophistication they have selected.
Level of sophistication increases from one through to three.
The assessment of data item sophistication in this Standard in not definitive and should be considered a
guide to agencies as they assess their minimum data requirements to meet a specific level of sophistication.
That is, each organisation will need to ascertain the applicability of the individual data items, identified
against the level of sophistication, with regards to the business requirements within its asset management
and investment practices.
To assist organisations to determine their target level of sophistication, guidance is provided in Figure 4.11.
Importantly, an organisations assessment of the required level of sophistication can be applied at an asset
portfolio or asset group level or asset component level, depending upon the organisation’s requirements.
Best results will generally be achieved by starting with assessment of sophistication requirements at an asset
group level.
Organisations wishing to utilise the sophistication guide in Figure 4.11 should complete the following three
steps:
1. Determine the level of assessment to be undertaken (i.e. asset portfolio, asset group or asset
component). If available, this step will be assisted by reference to the organisation’s asset
componentisation structure (or asset hierarchy);
2. Answer all questions, for each data aspect. Where the answer is “yes”, then place a tick in the boxes
adjacent to this question. There may be more than one box ticked, indicating that more than one level of
sophistication can deliver the required outcome; and
3. Once all the questions are answered for each data aspect, then assess the level of sophistication that is
most appropriate based upon the responses to the questions. If multiple levels of sophistication are
triggered, then the organisation will need to balance the degree of compromise against the cost of
implementation.
Careful consideration is to be given to the future organisational objectives in determining what might be an
appropriate level of sophistication.
Data Creation Data creation typically refers to the development of the inventory data that forms part
of the asset register. Data creation should to be informed by clearly documented data
specifications. For road 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 Data collection typically refers to the data required for asset management planning
purposes. Data collection should be informed by clearly documented data
specifications. This data is collected following asset acquisition (operations and
maintenance phase) and provides the base data for analysis of asset condition,
utilisation, and performance; and
Data Analysis Data analytics refers to the science of examining the raw data with the purpose of
drawing conclusions about that information. This information directly informs the asset
planning decision process.
Data Maintenance Data maintenance refers to the ongoing storage, updating, and reporting of data and
applies to all phases.
Figure 5.1 presents the three key data phases and their relevant function groups:
Road data can exist in three distinct states depending upon the data type:
Static Data Data that does not change over time (e.g. fixed inventory such as pavement
formation);
Dynamic Data Data that changes over time, however measured periodically (e.g. condition data); and
Real-time Data Data that is being measured on a continuous basis and is dynamically changing (e.g.
live traffic congestion or average speed monitoring)
6. Data Classes
Data type Type A classification identifying one of various types of data, such as
alphanumeric, integer or Boolean. The list of Data Types is defined in
table 6.3
Number Precision Precision Is the number of digits in a numerical value. For example, the number
123.45 has a precision of 5.
Number Scale Scale Scale is the number of digits to the right of the decimal point in a
number. For example, the number 123.45 has a scale of 2.
Data Item Units Units Only where relevant, the unit of measure for the item, for example
metres, centimetres, kilometres.
List of values List A list of allowable values will be provided for data items where the item
must be constrained to one of a set of values. E.g. the list of allowable
materials that a deck can be constructed from. (i.e. allowable list of
values)
Key Purpose for Data Item Purpose A category of the main purpose the data is used for. This is either:
L Location
D Descriptive
P Planning (forecasting the future asset state and financial liability)
I Optional descriptive data – ‘Information’
Sophistication Soph The assessed level of sophistication as defined in section 4. This is a
guide only and organisations will need to determine whether the data
item is applicable for its asset management practice.
Either 1, 2 or 3.
Industry Reference References The most relevant industry reference, which in most cases also formed
the basis for the related data items.
Prioritised Harmonised Set PHS Data item identified as a priority for implementation by Road Agencies
for industry benefit and effective asset management practice. Codes
represent:
N Network Reporting (input to a reported network measure).
M Management (asset and service).
Short Technical
Name Specification Precision Scale Definition
Code
alphanumeric AN(m) varchar(m) [a-z], [A-Z], [0-9], [-]
Letter and digits where m is the maximum
number of characters allowed.
E.g. AN(4) could be 34AB but not 456ABC
alpha A(m) varchar(m) [a-z],[A-Z],[-]
Alphabetical (letters only), where m is the
maximum number of characters allowed.
E.g. A (4) could be Fred but not Freda.
decimal DC(p,s) number(p,s) Fixed precision and scale numbers with
precision (p) and scale (s). Precision is the
maximum total number of decimal digits that
will be stored, both to the left and to the right of
the decimal point. It applies to numeric fields.
Length is the maximum length of characters
applied to non-numeric fields. Scale is the
number of decimal digits that will be stored to
the right of the decimal point. This number is
subtracted from ’p’ to determine the maximum
number of digits to the left of the decimal point.
E.g. Decimal(5,2) is 999.99 maximum.
integer I integer Positive whole numbers only
date D date Format DD/MM/CCYY
date time DT datetime Format DD/MM/CCYY:HH:MM:SS
money Mo number(12,2) 8 2 Dollars and cents
Note: For attributes the m, p and s are specified as separate metadata elements, but can be displayed as one.
The level of sophistication for the provision of location referencing data in not considered to be cumulative. Therefore, if an organisation is operating at level 3,
they are not required to provide the requirements for levels 1 and 2. The level of detail at a higher level is capable of providing that for the lower level. For
example, level 3 can provide the requirements for level 2 and/or 1.
Points
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Location loc_desr Location description if not A 100 L 1
description attached to a road, such as
Park name, property address
[Link] Location loc_dist Distance to the asset from the I 6 m L 1 M
distance road origin
[Link] Side loc_side Side of the road the asset is Left A 10 Code List 9.47 L 1
located on relative to the
defined network orientation
[Link] Offset loc_offset Distance from road centreline DC 3 1 m L 1
in metres
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Projection loc_proj Projection the data is reported NZTM2000 or AN 100 L 2
in including zone if MGA94 Zn 54
appropriate
[Link] Vertical datum loc_vert Vertical height datum used to AHD AN 100 L 2
report the data
[Link] X coordinate loc_x Y coordinate locator point at DC 9 2 m L 2 M
end of asset
[Link] Y coordinate loc_y Original coordinate system DC 9 2 m L 2 M
prior to transformation
[Link] Z coordinate loc_z Z coordinate (elevation) DC 9 2 L 3 M
locator point at centre of asset
Polylines
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Location loc_desr Location description if not A 100 L 1
description attached to a road, such as
Park name, property address
[Link] Start location loc_s Distance to the asset start I 6 m L 1
point relative to the network
orientation
[Link] End location loc_e Distance to the asset end I 7 m L 1
point from the road origin
[Link] Side of road start loc_s_si Side of the road the asset Left A 10 Code List 9.47 L 1
start is located on relative to
the defined network
orientation
[Link] side of road end loc_e_si Side of the road the asset end Left A 10 Code List 9.47 L 1
is located on relative to the
defined network orientation
[Link] Start lateral loc_dis_s Lateral offset measured from DC 3 1 m L 1
offset the road centreline at its start
location, in the increasing
direction of travel
[Link] End lateral offset loc_dis_e Lateral offset measured from DC 3 1 m L 1
the road centreline at its end
location, in the increasing
direction of travel
[Link] Start width loc_wid_s Width in metres of the asset DC 5 2 m L 1
at the start displacement
[Link] End width loc_wid_e Width in metres of the asset DC 5 2 m L 1
at the end displacement
[Link] Projection loc_proj Projection the data is reported NZTM2000 or AN 100 L 2
in including zone if MGA94 Zn 54
appropriate
[Link] Vertical datum loc_vert Vertical height datum used to NZVD 2009 AN 100 AHD, NZVD L 2 M
report the data 2009
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] X coordinate loc_x_s X coordinate locator point at DC 9 2 L 2 M
start start of asset
[Link] Y coordinate loc_y_s Y coordinate locator point at DC 9 2 L 2 M
start start of asset
[Link] Y coordinate end loc_x_e X coordinate locator point at DC 9 2 L 2 M
end of asset
[Link] X coordinate end loc_y_e Y coordinate locator point at DC 9 2 L 2 M
end of asset
[Link] Z coordinate loc_z_s Z coordinate locator point at DC 9 2 L 3 M
start centre of asset
[Link] Z coordinate end loc_z_e Z coordinate locator point at DC 9 2 L 3 M
centre of asset
Polygons
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Location loc_desr Location description if not A 100 L 1
description attached to a road, such as
Park name, property address
[Link] Start location left loc_l_s Distance to the asset start I 6 m L 1
point, left hand side, relative
to the defined network
orientation
[Link] Start location loc_r_s Distance to the asset start I 6 m L 1
right point, right hand side, relative
to the defined network
orientation
[Link] End location left loc_l_e Distance to the asset end I 6 m L 1
point from the road origin, on
the left-hand side
[Link] End location right loc_r_e Distance to the asset end I 6 m L 1
point from the road origin, on
the right-hand side
[Link] Start lateral loc_l_s_of Lateral offset measured from DC 3 1 m L 1
offset left the centreline to the left
corner at its start location.
Side is determined by the
direction of increasing
distance along the link
[Link] Start lateral loc_r_s_of Lateral offset measured from DC 3 1 m L 1
offset right the centreline to the right
corner at its start location.
Side is determined by the
direction of increasing
distance along the link
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] End lateral offset loc_l_e_of Lateral offset measured from DC 3 1 m L 1
left the centreline to the left
corner at its end location
asset. Side is determined by
the direction of increasing
distance along the link
[Link] End lateral offset loc_r_e_of Lateral offset measured from DC 3 1 m L 1
right the centreline to the left
corner at its end location.
Side is determined by the
direction of increasing
distance along the link
[Link] Projection loc_proj Projection the data is reported NZTM2000 or AN 100 L 2
in including zone if MGA94 Zn 54
appropriate
[Link] Vertical datum loc_vert Vertical height datum used to AHD AN 100 L 2 M
report the data
[Link] X coordinate loc_x_s_l X coordinate locator point at DC 9 2 L 2
start left start of asset left hand side
[Link] Y coordinate loc_y_s_l Y coordinate locator point at DC 72 L 2
start left start of asset left hand side
[Link] X coordinate loc_x_s_r X coordinate locator point at DC 9 2 L 2
start right start of asset left hand side
[Link] Y coordinate loc_y_s_r Y coordinate locator point at DC 9 2 L 2
start right start of asset right hand side
[Link] X coordinate end loc_x_e_l X coordinate locator point at DC 9 2 L 2
left end of asset left hand side
[Link] Y coordinate end loc_y_e_l Y coordinate locator point at DC 9 2 L 2
left end of asset left hand side
[Link] X coordinate end loc_x_e_r X coordinate locator point at DC 9 2 L 2
right end of asset right hand side
[Link] Y coordinate end loc_y_e_r Y coordinate locator point at DC 9 2 L 2
right end of asset right hand side
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Z coordinate loc_z_s_l Z coordinate (elevation) DC 7 2 L 3
start left locator point at start of asset
left hand side
[Link] Z coordinate loc_z_s_r Z coordinate (elevation) DC 7 2 L 3
start right locator point at start of asset
right hand side
[Link] Z coordinate end loc_z_e_l Z coordinate (elevation) DC 7 2 L 3
left locator point at end of asset
left hand side
[Link] Z coordinate end loc_z_e_r Z coordinate (elevation) DC 7 2 L 3
right locator point at end of asset
right hand side
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
7.2.1 Data date dat_date The date the data was D 100 P 1
originally collected and
recorded.
7.2.2 Data owner dat_owner The owner of the data. AN 100 P 1
7.2.3 Data source dat_source The original source of the AN 100 P 1
data.
7.2.4 Data confidence dat_confid The implied confidence of the A 100 Code List 9.8 P 1
data as determined by the
method of data creation.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
7.2.5 Data editor dat_editor The person who entered the AN 100 P 1
data into the database.
7.2.6 Data editor dat_edit The date the data was last D 100 P 1
edited.
Overview
All road agencies need to define its road network in terms of the road links and their connectivity. This network model provides the basis for route planning
and referencing network related data that cannot be directly associated with road based assets.
Scope
This section provides the data items that describe the road network including the links and link sections that form the basis for the network. The road network
model is the prime location reference for most asset related function groups. Section 4.1 provides guidance on how to define the road network including
detailed information on a topologic model.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Network
8.1.1 Network Name network_na Name of the road network Example City A 50 L 1 M
Council
Node
8.1.2 Node ID node_id Unique reference identifier for 1234567 I 10 L 1 M
the network node
8.1.3 X coordinate start node_x_s The X coordinate locator point DC 9 2 L 1 M
node that defines the start node of a
road
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.1.4 Y coordinate node_y_s The Y coordinate locator point DC 9 2 L 1 M
start node that defines the start node of
a road
8.1.5 Z coordinate node_z_s The Z coordinate (elevation) DC 7 2 L 1 M
start node locator point that defines the
start node of a road
8.1.6 X coordinate end node_x_e The X coordinate locator point DC 9 2 L 1 M
Node that defines the end node of a
road
8.1.7 Y coordinate end node_y_e The Y coordinate locator point DC 9 2 L 1 M
Node that defines the end node of a
road
8.1.8 Z coordinate end node_z_e The Z coordinate (elevation) DC 7 2 L 1 M
Node locator point that defines the
end node of a road
Link
8.1.9 Link ID link_id Unique reference identifier for I 10 L 1
the network link between two
nodes. Every link must have a
start node and an end node
8.1.10 Link traffic flow link_tflow The flow direction of traffic on One way AN 50 Code List 9.61 L 1
the link. This can either be decreasing
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
8.1.11 Link length link_len The actual distance between I 6 m D 1
the start and end node for a
road. This is the link length
Road
8.1.12 Road ID road_id Unique reference identifier for I 10 L 1 M
an existing road
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.1.13 Road name road_name Road name spelled in full, no Jones Drive A 100 L 1 M
abbreviations for type of road.
For subdivision roads, the
proposed name can be
available from the
organisation it will be vested
to
8.1.14 Road Length road_len Total length of road network, I 7 km P 1 NM
measured in kilometers.
Divided carriageways in
excess of 200m are
considered separate roads in
forward and reverse
directions.
8.1.15 Lane Kilometre lanekm_len Total length of road network, I 7 km P 2 NM
Length measured in lane kilometers.
Hard shoulders are not
considered a lane, unless
they are signed for periodic
use during peak periods.
8.1.16 Number of Major no_str_tot Total number of major I 6 # P 1
Structures structures across the road
network, including bridges
and major culverts.
8.1.17 Number of no_str_bri Total number of bridges I 6 # P 1 NM
Bridge Structures across the road network.
8.1.18 Number of Major no_str_cul Total number of major I 6 # P 1 NM
Culvert culverts across the road
Structures network.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Link Section
8.1.19 Link section ID link_s_id A link that is broken into more I 10 L 1 M
than one part creates a link
section. Each link section has a
unique ID to identify it. Where
only one link exists between
nodes there is no link section,
or link section ID
8.1.20 Link section start link_s_s The start displacement of the I 6 m L 1 M
displacement link section as determined by
the network orientation
8.1.21 Link section end link_s_e The end displacement of the I 6 m L 1 M
displacement link section as determined by
the network orientation
8.1.22 Link section link_s_len The length of the link section I 6 m D 1 NM
length calculated by deducting the
link section end displacement
from the link section start
displacement
8.1.23 Link section link_s_wid The weighted average width DC 3 1 m D 1 M
average width of the link section measured
between edge of pavement to
edge of pavement for
unsealed roads. For sealed
roads from edge of seal to
edge of seal where no kerb is
present, or kerb face to kerb
face.
8.1.24 Link section link_s_uni An indicator that represents A 1 U - uniform D 1
uniform width the consistency in the link width, V -
section width. Where the varying width
measured width variation is
less than 1.0m use uniform,
and if greater use varying
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.1.25 Reserve width res_wid_l The lateral offset distance 10.5 DC 3 1 m D 1
left from from the road centreline to the
centreline left side of the corridor
reserve boundary. Side is
determined by the network
orientation
8.1.26 Reserve width res_wid_r The lateral offset distance 10.5 DC 3 1 m D 1
right from from the road centreline to the
centreline right side of the corridor
reserve boundary. Side is
determined by the network
orientation
8.1.27 Number of lanes links_lanl Number of trafficable lanes 2 I 1 # D 1 M
left of centreline within the link section, left of
the centreline
8.1.28 Number of lanes links_lanr Number of trafficable lanes 2 I 1 # D 1 M
right of centreline within the link section, right of
the centreline
8.1.29 Average lane links_llr Average width of trafficable 2 I 2 1 m D 1 M
width left of lanes, within the link section,
centreline left of the centreline
8.1.30 Average lane links_lwr Average width of trafficable 2 I 2 1 m D 1 M
width right of lanes, within the link section,
centreline right of the centreline
8.1.31 Separate link links_div Identifies if the carriageway A 1 D – divided, U D 1 M
sections for for vehicle flow in the opposite - undivided
traffic flow direction is separated by
direction means of a physical barrier
(divided), or undivided (no
physical barrier)
8.1.32 Traffic flow traf_dir One way or two-way traffic O- One way A 1 Code List 9.61 D 1 M
direction
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.1.33 Traffic setting traf_set Urban or rural indicator for the A 1 U - posted D 1 NM
link section speed limit <
or = 70km/hr,
R - posted
speed limit >
70km/hr
8.1.34 Type of pave_const The type of pavement on the A 3 Code List 9.70 D 1 M
pavement link section
construction
8.1.35 Ownership owner The link section that defines A 30 D 1 M
organisation the ownership location of a
road
8.1.36 Operator operator The link section that defines A 30 D 1
organisation the operator location of a road
8.1.37 Maintainer maintainer The link section that defines A 30 D 1
organisation the maintainer location of a
road
8.1.38 Maintenance maint_con The link section that defines AN 10 D 2
contract reference the maintenance location of a
road
8.2 Classification
Overview
Classification for a transport network/system attributes to each component link a functional priority or status level within the network. Any network will
generally include links classified at most levels across this spectrum within it. In this Standard the New Zealand One Network Road Classification (ONRC) has
been used as an example of a classification system.
Scope
The naming system for each status level used varies across National, State, and Local Authorities but the approach in each case will have the highest level for
network links that are strategic with high volumes that deliver economic or community benefits. At lower levels the links provide almost purely local access that
delivers local or private benefits. Between these two extremes are identified levels that combine and acknowledge compromises between general benefits
(through traffic flow) and local benefits (property access) at differing levels.
Higher order links tend to be costlier to maintain and operate but comprise a far smaller percentage by length of the network. Priority at the higher order links
is to support economic outcomes through traffic flow, at the expense of access and local use. In lower order links, access and local use increases, at the
expense of through traffic flow efficiency. Increased priority is given to shared access and dedicated space for non-car based travellers, such as pedestrians
and cyclists, as the classification hierarchy decreases.
Data items are provided for different organisational activities and are structured by intended use:
• In a land use planning context classification is used to define the purpose of the link and then attach suitable development limits or rules that support or
protect that purpose;
• In a network modelling context classification is used to describe the way a road is expected to support the network operation; the levels of classification
will reflect expected operational performance; and
• In a funding context, although all network components may justify some funding, higher level classification can be used to justify higher investment, more
significant improvements, more urgent/responsive maintenance, and closer monitoring.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Functional
8.2.1 Functional ctype_onrc The functional classification National A 6 Code List 9.19 D 1
Classification - for the carriageway section
One Road as defined in the One
Classification Network Road Classification
System system
Economic and Social
8.2.2 Estimated pop The estimated population I 7 # D 1
population served by the road as
served by road determined by a catchment
analysis
8.2.3 Criticality crit_conn A Boolean function returning Y - Yes B 1 Y or N D 1
positive if the route has
been identified by the road
manager as serving a critical
social, economic or
functional need. Road links
to remote regions or is sole
connectivity in urban areas;
or roads that have no
alternative routes
8.2.4 Freight value in fr_sig_val The estimated gross value Y - Yes B 1 Y or N D 1
motion of freight using the route per
annum. Freight value > $3B
8.2.5 Freight weight in fr_sig_wgt The estimated gross mass I 2 MT D 1
motion of freight using the route per
annum
8.2.6 Airport access air_pass The estimated number of I 8 # D 1
passengers in airport passengers using the
motion route per annum
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.2.7 Tourist route tourism A Boolean function returning Y - Yes B 1 Y or N D 1
a positive where a route is
either a) identified as a
scenic or tourist route in a
regional tourist strategy or b)
provides access to 5 tourist
destinations designated in a
regional tourist strategy.
Road serves top 5 tourist
destinations or has
regional/local significant
tourist destinations or
significant scenic routes
8.2.8 Hospital Access hospitals A Boolean function returning Y - Yes B 1 Y or N D 1
Road positive where a route is a
primary or secondary
access to a hospital,
ambulance depot or other
medical centre that provides
emergency response. Road
provides access to tertiary
or regional hospitals
8.3 Inventory
Overview
Inventory is the basic information about assets that includes describing the location, type and attributes of the asset. Asset inventory information is
fundamental to making informed asset management decisions, and it’s associated reporting. Asset inventory elements and associated components are
therefore critical for aggregated asset reporting, service standards, asset performance measurement or asset management activities.
Scope
Road Corridors comprise different asset groups and each of those groups have a number of characteristics describing the various components. This data is
used to create the Asset Register and in the context of this project will be referred to as the Inventory. Inventory data is required as a result of subdivision
development; works or programs such as minor or major capital works, renewals and maintenance activities. It is “as constructed” data that is provided as a
record, at a particular point in time.
The data items that are common to all asset groups have been separately identified as common classes.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
General
[Link] Unique asset asset_id The unique asset identifier AN 20 D 1 NM
identifier
[Link] Asset class asset_clas The asset class or group Bridge A 20 Code List 9.2 D 1 NM
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Construction const_co Construction Company name Jamieson A 100 D 1
Organisation only Construction
name
[Link] Design Company design_co Design Company name only Fred Charles & A 100 D 1
name Associates
[Link] Subdivision stage_no Subdivision or Project Stage 7 or 3B AN 10 D 1
stage or project Number. Field can be used
number for either a subdivision or
capital works project.
[Link] Design life life_cons The design life expected at I 3 P 2 M
the time of construction /
installation
Valuation
[Link] Construction const_date Date the asset was D 8 dd/mm/ccyy P 2 M
date constructed/built/ installed
[Link] Construction const_cost Construction cost in 1000000 Mo 10 2 $ P 2 M
cost Australian/New Zealand
Dollars. Currency is to be
relevant to the jurisdiction.
[Link] Operation status asset_stat Current operational state of ABN - A 30 Code List 9.3 P 2 M
the asset. Abandoned
[Link] Financial currency Currency used to estimate AUD Mo 10 2 $ AUD or NZD P 2
currency costs (Australian
Dollars)
[Link] Valuation type value_type Valuation type RC - A 4 Code List 9.73 P 2 NM
Replacement
Cost
[Link] Assessed cost in value Assessed cost in 1000000 Mo 10 2 $ P 2 NM
Australian/New Australian/New Zealand
Zealand Dollars Dollars. Currency is to be
relevant to the jurisdiction.
[Link] Unit cost unit_cost Cost per unit of the asset 130.25 Mo 10 2 $ P 2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Valuation year value_year The date the valuation was ddmmyyyy D 8 yr P 2 M
undertaken
Additional Information
[Link] Comments comments Any additional comments that AN 250 I 3
relate to this asset
[Link] Photo reference photo_ref Reference photograph of dd/mm/ccyy AN 100 I 3
asset. [description].jpg
[Link] Data editor added_by The person who added the A 20 I 3
data to the asset register
[Link] Data added date added_date The date the data was added ddmmyyyy D 8 I 3
to the asset register
[Link] Vesting date vest_date The date the asset was vested ddmmyyyy D 8 I 3 All
(ownership transfer) to the
road agency
[Link] Vesting source vest_org The organisation gifting A 20 I 3 [Link]
(vesting) the asset to the road
agency
Amenities
A feature or facility that is provided in a location that is not covered by the other asset groups (i.e. gas BBQ).
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Type amen_type Amenity Type A 100 Code List 9.28 D 1
[Link] Material amen_mat Material made out of Steel A 100 Code List 9.26 D 2
[Link] Manufacturer amen_manuf Company name only Lunds Pty Ltd A 100 I 3
[Link] Model number amen_model Model number JK-001-A AN 30 I 3
Bins
A receptacle that is used to store litter and is emptied at a determined frequency. It is often placed on the footpath, or grass berm area.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Capacity bin_cap Bin Capacity in Litres 240 I 3 L D 1
[Link] Type bin_type Bin Type SR A 100 D 1
[Link] Bin intended use bin_use The intended use of the bin. Recycle A 20 Code List 9.3 P 1
Recycle, waste, glass only,
green clippings etc.
[Link] Liner present bin_liner A bin liner is present N - No B 1 Y or N I 2
[Link] Manufacturer bin_manuf Manufacturing company BIF Pty Ltd A 100 I 3
name only
[Link] Material bin_mat Material the bin is made out of Steel A 100 Code List 9.26 I 2
[Link] Model number bin_model Model number Ef-456-S AN 30 I 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Supplier bin_suppl Bin Supplier Visy AN 100 I 3
A structure designed to provide passage for road users over an obstacle by spanning it. Major culverts have a cross sectional area of more than 3.4 sq.m.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Bridge Width br_wid_l The lateral offset distance DC 3 1 m L 1
Left of from the road centreline to
Centreline the left hand extent of the
bridge. Side is determined
by the direction of
increasing distance along
the link
[Link] Bridge Width br_wid_r The lateral offset distance DC 3 1 m L 1
Right of from the road centreline to
Centreline the right-hand extent of the
bridge. Side is determined
by the direction of
increasing distance along
the link
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Waterway ww_name Populate the waterway A 100 L 1
Name name if a waterway passes
through the culvert or
beneath the bridge
[Link] Beam Material beam_mat For a bridge the material CONC - A 100 D 1
the beam is constructed of. Concrete
Populate only if
Bridge/Major Culvert
Components is not used
[Link] Column or Pile br_col_mat For a bridge the material CONC - A 100 Code List D 1
Material the column or pile is Concrete 9.27
constructed of. Populate
only if Bridge/Major Culvert
Components is not used.
[Link] Deck Material br_dek_mat For a bridge the material Wood A 100 Code List D 1 NM
the deck is constructed of. 9.27
Populate only if
Bridge/Major Culvert
Components is not used.
[Link] Earthquake br_eq_rate Earthquake rating of the DC 6 2 D 1
Rating structure
[Link] Foundation br_fnd_mat Foundation material A 100 D 1
material
[Link] Foundation br_fnd_typ Foundation type A 30 D 1
type
[Link] Entrance Gate br_gate The bridge has a gate at Y - Yes B 1 Y or N D 1
the entrance
[Link] Number of br_beam_no Number of beams 6 I 2 # D 1
Beams
[Link] Number of br_col_no Number of columns or piles 8 I 2 # D 1
columns or
Piles
[Link] Number of br_pier_no Number of piers 4 I 2 # D 1
Piers
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Pier Material br_pie_mat Pier material. Populate only CONC - A 100 D 1
if Bridge/Major Culvert Concrete
Components is not used.
[Link] Safety Rail br_rai_mat Safety rail material Steel A 30 D 1
Material
[Link] Safety Rails br_rail The structure has safety Y - Yes B 1 Y or N D 1
Present rails
[Link] Cell Type For br_cel_typ If a major culvert the type of Box A 30 Code List D 2
Major Culvert culvert structure. Populate 9.31
only if Bridge/Major Culvert
Components is not used.
[Link] Vertical br_clear Distance between water DC 6 2 D 2
Clearance feature and the bridge at
the high water mark in
metres.
In the event of inland water
at high water mark or tidal
water at high tide. Populate
only for a bridge if it is over
a watercourse.
[Link] Function of the br_func Function of the feature OR - Over A 100 Code List D 2
Feature Road 9.19
[Link] Number of br_spans Number of spans of the 3 I 2 # D 2
Spans or Cells bridge or number of cells of
the major culvert
[Link] Feature br_struc Feature Structure Type. Stock A 100 Code List 9.5 D 2 M
Structure Type crossing/
underpass
[Link] Cell Material br_cel_mat Populate only if the Pre-cast A 30 D 3
For Major structure is a major culvert Concrete
Culvert and if Bridge/Major Culvert
Components is not used.
[Link] Length br_len Total length of the structure 20.5 DC 4 2 m D 3 NM
in metres
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Width br_wid Total width of the structure 2.45 DC 5 2 m D 3 M
in metres
[Link] State Or br_heritag The structure is in the state Y - Yes B 1 Y or N P 1
National or national heritage listing
Heritage Listing
[Link] Vehicular Load br_ld_lim Vehicular gross load limit 250 I 5 kg P 1 M
Limit on the structure.
[Link] Abutment br_abu_mat Abutment material. CONC - A 100 I 2
Material Populate only if Concrete
Bridge/Major Culvert
Components is not used.
[Link] Area br_area Area of the component in 25.35 DC 6 2 sq.m D 1
square metres if the
dimensions are not uniform
[Link] Height br_hei Height of the component in 2300 I 4 mm D 1
mm
[Link] Length br_co_len Length of the component in 6.23 DC 4 2 m D 1
metres
[Link] Number of br_comps Number of same type of 4 I 2 # D 1
components components with the same
dimensions and material
[Link] Width br_wid_co Width of the component in 2.45 DC 5 2 m D 1
metres
[Link] Component br_co_type Component type TB - T A 30 Code List 9.7 D 3
type Beam,
[Link] Component br_co_mat Component material Wood A 100 Code List D 3
material 9.27
[Link] Component br_co_code Structure component code 1S - Steel AN 6 Code List 9.6 I 3
code according to the Bridge box girder
Inspection Manual used in
each jurisdiction
Culverts (Minor)
One or more adjacent pipes or enclosed channel that conveys surface water run-off, or a stream, below the formation level of a road. Minor culverts have a
cross sectional area of less than 3.4 sq.m.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Downstream Pit cul_pit_no Downstream Pit Number. This AN 15 L 1
Number number must form part of the
Pipe section number.
[Link] Downstream X cul_dn_x Downstream end-of-pipe X DC 9 2 L 2
Coordinate Coordinate. Will be used in
the computation check of the
pipe length
[Link] Downstream Y cul_dn_y Downstream end-of-pipe Y DC 9 2 L 2
Coordinate Coordinate. Will be used in
the computation check of the
pipe length.
[Link] Upstream X cul_up_x Upstream end-of-pipe X DC 9 2 L 2
Coordinate. Coordinate. Will be used in
the computation check of the
pipe length
[Link] Upstream Y cul_up_y Upstream end-of-pipe Y DC 9 2 L 2
Coordinate Coordinate. Will be used in
the computation check of the
pipe length
[Link] Internal pipe cul_dia Internal pipe Diameter of the 450 I 4 mm D 1
Diameter or pipe or Width if the pipe is
Width non-circular
[Link] Non Circular cul_hei Pipe Height. Needs to be 450 I 4 mm D 1
Pipe height populated for non-circular
pipes
[Link] Pipe section cul_len Pipe section length in metres 100.55 DC 5 2 m D 1
length
[Link] Pipe material cul_mat Pipe material. RC A 100 Code List 9.26 D 1
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Unique number cul_pit_no Unique number in this Stage 37-38A AN 30 D 1
derived from pit derived from pit numbers. The
numbers downstream (1st number)
should generally be smaller
than the upstream (2nd
number). i.e. Pipe Section 13 -
14. As a rule of thumb, the
"downstream-up" principal
should be followed when
numbering the pipe sections.
[Link] Pipe type cul_type Pipe type. Pipe, open, A 100 Code List 9.31 D 1
culvert,
subsoil
[Link] Pipe cul_config This field ONLY needs to be Example 1. - AN 50 D 2
configuration populated when the pipe Configuration
configuration inside a SWALE of
trench or Culvert contains conduits/pipes
more than 1 (one) pipe in culverts
3x150
i.e. 3 conduits
/ pipes @
150mm
diameter
each.
Example 2. -
Configuration
of conduits/
pipes in
culverts
3x150x300
i.e. 3 conduits
/ pipes @
150mm
diameter/width
by 300 height
each.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Structure location cul_in_out This field ONLY needs to be Outlet backflow A 50 D 2
populated when an inlet or prevention
outlet structure exists. Describe valve. Outlet
extent of inlet, outlet or other energy
feature. reducing
device.
[Link] Pipe shape cul_shape Shape of the pipe A 10 Code List 9.30 D 2
[Link] Upstream Pit cul_up_pit Upstream Pit Number. This AN 15 D 2
Number number must form part of the
Pipe section number
[Link] 2nd pipe cul_dia_2 Populate ONLY when the 200 I 4 mm D 2
diameter pipe type is non circular and
has two diameters.
For egg shaped pipes
(W1 = Dia_Width ; W2 =
Width2 ; H = Height)
[Link] Downstream cul_dn_inv Downstream end-of-pipe Invert DC 5 2 D 3
Invert Level Level. When recording the
invert levels, it stands to
reason that the downstream
invert level must be smaller
than the upstream invert level.
[Link] Relined or cul_in_mat Relined or renewed material Fibreglass A 30 I 2
renewed material
[Link] Relining or cul_in_met Relining or renewal method CUREDIP - A 100 CUREDIP - I 3
renewal method Cured in place Cured in place
SLUPVC - Slip
lined with
uPVC &
grouted
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Upstream end-of- cul_up_inv Upstream end-of-pipe Invert DC 5 2 D 3
pipe Invert Level Level. When recording the
invert levels, it stands to
reason that the downstream
invert level must be smaller
than the upstream invert level.
Fences
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.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Drop protection fen_prot If the fence provides A 1 D 1
protection to large drops
[Link] Type fen_typ Fence type Post and rail, A 100 Code List 9.17 D 1
rail, electric,
picket, post
and wire etc.
[Link] Function fen_func Fence function SEC - A 100 Code List 9.16 D 2
Security
[Link] Height fen_hei Height of the fence in metres 2.1 DC 5 2 m D 3
[Link] Length fen_len Length of the fence DC 4 2 m D 3
[Link] Material fen_mat Fence material Wrought Iron A 100 Code List 9.26 D 3
[Link] Joint ownership fen_joint Is the fence in joint ownership A 1 I 3
[Link] Manufacturers fen_manuf Manufacturers name Streetsmart A 100 I 3
name Group Ltd
ITS Assets
Point Assets
An Intelligent Traffic Systems asset or component that is defined by a point (i.e. it has no length).
Polyline Assets
An Intelligent Traffic Systems asset or component that has a start and end point, and an associated length.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
General
[Link] Site name its_site Site name A 30 L 1
[Link] Type its_type Asset ITS Component Type CCTV A 100 D 1
[Link] Above or below its_abobel Height above surface or DC 4 2 m D 2
surface level depth below surface. +ve
number if above ground, -ve if
below
[Link] Access its_access Access requirements Traffic A 30 I 2
requirements Management
[Link] Power source its_power Power source Main A 30 Code List 9.35 I 1
Polyline
[Link] Contractor its_l_suid Contractor ID AN 30 D 1
suppliers unique
ID
[Link] Contractors its_l_coid Contractor’s Unique ID of the AN 30 D 1
unique ID ‘Asset_To’ asset
[Link] Controller ID its_l_cnid Controller ID AN 30 D 1
[Link] Conduit length its_l_len Conduit section length in DC 4 2 m D 1
metres (m)
[Link] Housing type its_l_type Housing type Conduit A 30 D 2
[Link] Conduit material its_l_clen Conduit material. Copper A 100 Code List 9.26 D 2
[Link] Defects liability its_l_liae End date of defects liability ddmmyyyy D 8 P 1
end date period
[Link] Design life its_l_dl Design life length in years 5 I 3 P 2
[Link] Maintenance its_l_mreq Maintenance requirements A 100 P 2
requirements
[Link] Defect liability its_l_lias Starting date of defects ddmmyyyy D 8 P 3
start date liability period
[Link] Installer its_l_ints Installer A 30 I 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Manufacturer its_l_manu Manufacturer A 100 I 3
[Link] Supplier its_l_supp Supplier A 30 I 3
[Link] Warranty end its_l_wend Warranty end date ddmmyyyy D 8 I 2
date
Point
[Link] Controller ID its_p_cnid Controller ID DT13426 AN 30 D 1
[Link] Control system its_p_type Control system type A 30 D 1
type
[Link] Data logger its_p_log A data logger is present Y - Yes B 1 Y or N D 1
present
[Link] Connected radar its_p_rad Whether a Radar Unit is Y - Yes B 1 Y or N D 1
unit connected or not
[Link] Unique ID of the its_p_uniq Unique ID of the asset RNDG367 AN 30 D 1
asset
[Link] Communication its_p_comm Communication method. Bluetooth A 30 D 3
method Bluetooth, microwave
[Link] Housing type its_p_htyp Housing type Conduit A 30 D 3
[Link] UPS is its_p_ups Whether a UPS is connected Y - Yes B 1 Y or N D 3
connected or not
[Link] Design life in its_p_des Design life length in years 25 I 4 P 1
years
[Link] Defects liability its_p_liae End date of defects liability ddmmyyyy D 8 P 1
end date period
[Link] Maintenance its_p_mreq Maintenance requirements A 100 P 1
requirements
[Link] Start date of its_p_lias Starting date of defects ddmmyyyy D 8 P 1
defects liability liability period
period
[Link] Installer its_p_ints Installer A 30 I 3
[Link] IP address its_p_ipad IP address [Link] AN 30 I 2
[Link] Manufacturer its_p_manu Manufacturer A 100 I 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Model number its_p_mod Model number AN 30 I 2
[Link] Mounting type its_p_moun Mounting type A 30 I 3
[Link] Pin number or its_p_pass Pin number or password AN 30 I 2
password
[Link] Serial number its_p_seri Serial number AN 30 I 3
[Link] Supplier its_p_supp Supplier A 30 I 3
[Link] Warranty end its_p_ware Warranty end date ddmmyyyy D 8 I 3
date
Polygon
[Link] Communication its_pl_com Communication method. Microwave A 30 D 2
method Bluetooth, microwave
[Link] Control system its_pl_cs Control system type A 30 D 2
type
[Link] UPS is its_pl_ups Whether a UPS is connected Y - Yes B 1 Y or N D 2
connected or not
The kerb and channel combine to form a surfaced open drain to capture and discharge run off from the road.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Material kc_mat Kerb material CONC - A 100 Code List 9.26 D 1
Concrete
[Link] Type kc_typ Kerb Type Mountable A 100 Code List 9.22 D 1
Kerb
[Link] Width kc_wid With of the kerb excluding the 100 I 3 mm D 1
channel. Channel width is
included in the link
dimensions
[Link] Length kc_len Length of the kerb in metres 30.25 DC 4 2 m D 3
[Link] Responsible kc_resp The name of the responsible A 100 I 1
Authority Authority for maintenance
purposes.
Landscaping
Areas that have been modified for visual effect and typically include planting or vegetation such as gardens. It can also include hard landscaping.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Depth land_dep Depth of the material where I 4 mm D 1
the landscaping feature does
not contain water. Or the
average depth of water for a
water feature. Height of the
hedge if the feature is a
hedge
[Link] Material land_mat Material Fibreglass A 100 Code List 9.26 D 1
[Link] Type of land_typ Type of Landscaping A 100 D 1
Landscaping
Lighting
Assets that primarily provide illumination to the road surface for the purpose of safety.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Bracket height l_brk_hei Height from the ground to the 6.32 DC 5 2 m D 1
bottom of the bracket
[Link] Bracket length l_brk_len Length of the bracket 1200 I 4 mm D 1
[Link] Connection Type l_conn_typ Connection Type AGND - A 10 D 1
Above ground
[Link] Luminaire l_cap Luminaire capacity I 3 D 1
capacity
[Link] Luminaire model l_model Luminaire model type A 100 D 1
type
[Link] Number of l_lum_num Number of luminaires 2 I 2 # D 1
luminaires
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Pole type l_pole_typ Pole type PEDEST - A 30 PEDEST - D 1
Pedestal Pedestal
CANT -
Cantilever
[Link] Connected to l_smart_gd The light is connected to a Y - Yes B 1 Y or N D 1
smart grid smart grid
[Link] Lighting Type l_typ Lighting Type Directional A 100 Code List D 1
9.23
[Link] Luminaires l_wattage Wattage of the Luminaires. 100 I 3 Watt D 1
wattage
[Link] Control Point l_icp_no Installation Control Point AN 30 P 1
number number
[Link] Bracket angle l_brk_ang Angle of the bracket clockwise 125 I 3 degrees I 2
from bracket to pole
[Link] Bracket material l_brk_mat Bracket material A 30 I 2
[Link] Bracket mounting l_brk_mnt Mounting type of the bracket A 30 I 2
type
[Link] Bracket l_brk_orie Orientation of the bracket. 225 I 3 degrees I 2
Orientation Angle from North, clockwise
to the bracket (its bearing).
[Link] Bracket type l_brk_typ Bracket type A 30 I 2
[Link] Bulk circuit l_conn Bulk circuit connection A 30 I 2
connection
[Link] Light colour l_col Light colour A 30 I 1
[Link] LED chip l_led_manu LED chip manufacturer. ABC A 30 I 3
manufacturer Manufacturing
[Link] Luminaire l_manuf Luminaire manufacturer IBEX Co. A 100 I 3
manufacturer
[Link] Manufacturer l_manu_imp Name of the Manufacturer or Australian A 100 I 3
Importer name Importer Lighting
Company
[Link] Power supply l_power_co Power supply company. Power Co. A 30 I 1
company
[Link] Light shade type l_shd_typ Light shade type A 30 I 2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Lighting design l_des_std Standard the light is designed A 30 I 3
standard to
[Link] Upcast angle l_tilt_ang Upcast angle, clockwise from 20 I 3 degrees I 3
horizontal. Horizontal = 0
degrees
Line-Marking Assets
Lines, painted or otherwise applied, that delineate lane boundaries and guide traffic with respect to overtaking and the like. These markings have a start and
end point and a corresponding length.
Polyline Assets
Point Assets
Lines, painted or otherwise applied, that delineate lane boundaries and guide traffic with respect to overtaking and the like. Point assets are typically symbols etc.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
General
[Link] Audible lin_aud The marking has audible Y – Yes B 1 Y or N D 2
capability
[Link] Colour lin_colour Colour of the line marking White A 30 D 2
[Link] Reflect lin_refl The marking is reflectorized Y – Yes B 1 Y or N D 2
[Link] Spacing lin_spcng Spacing between two spacing between I 4 mm D 2
markings in the polygon two diagonal or
chevron markings
(600mm)
[Link] Type lin_typ Type of marking Chevron A 100 D 2
[Link] Application Rate lin_app_r Application rate used when DC 6 2 I 3
painting the marking in
square metres per second
(m2/s)
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Manufacturer lin_manuf Manufacturer of the paint A 100 I 3
used for marking
[Link] Paint Brand lin_paint Brand name of the paint A 30 I 3
used for marking
Polylines and Polygons
[Link] Thickness lin_thick Thickness of the line in 200 I 3 D 1
microns (1x10-6m)
[Link] Width linem_wid Width of the line 100 I 3 mm D 1
Point
[Link] Thickness line_p_thi Thickness of the line in 200 I 3 D 1
microns (1x10-6m)
Point Assets
Mechanical and electrical asset sub-components. They are often connected to other assets such as tunnels. Point assets have no length.
Polyline Assets
Mechanical and electrical asset sub-components. They are often connected to other assets such as tunnels. Linear assets have a start and end point with an
associated length.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
General
[Link] Site name me_site Site name A 30 L 1
[Link] Absolute Surface me_ab_surf Height above surface or DC 4 2 m D 1
height depth below surface. +ve
number if above ground, -ve if
below
[Link] Asset sub type me_sub_typ The asset sub type Fire A 30 Code List 9.24 D 1
Protection -
Foam System
Lines
[Link] Type me_typ Asset Component Type Fire A 100 D 1
[Link] Design life me_des_lif Design life length in years 20 I 2 Yr P 1
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Point
[Link] Communication me_commtyp Communication method. Bluetooth A 30 D 1
method Bluetooth, microwave
[Link] Controller ID me_cont_id Controller ID AN 30 D 1
[Link] Control system me_cs_typ Control system type A 30 Code List 9.24 D 1
type
[Link] Data logger me_dat_log Whether there’s a data logger Y - Yes B 1 Y or N D 1
present present
[Link] Housing type me_housing The housing type present Cabinet A 30 D 1
[Link] UPS is me_ups A UPS is connected Y - Yes B 1 Y or N D 1
connected
[Link] Purchase date me_purch Purchase date ddmmyyyy D 8 P 1
[Link] Model number me_mod_no Model number AN 30 I 3
[Link] Mounting type me_mount Mounting type A 30 Code List 9.24 I 3
[Link] Power source me_power Power source Grid A 30 Code List 9.35 I 1
[Link] Serial number me_seri_no Serial number AN 30 I 2
[Link] Supplier me_supp Supplier A 30 I 3
[Link] Warranty end me_warrend Warranty end date ddmmyyyy D 8 I 3
date
Parking
The purpose, method of control, and restriction type are recorded for designated on road, off road parking areas.
L1
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Bay number bays Number of parking bays in a I 3 D 1
parking area
[Link] Metered parking meter Parking is controlled by a Y - Yes B 1 Y or N D 1
meter
[Link] Purpose purpose Purpose of the car park. Disabled A 20 Code List 9.27 D 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Type park_type Type of car park ONRD - On A 100 ONRD - On D 3
Road Road
OFFRD - Off
Road
[Link] Permit permits Permit parking present at this Y - Yes B 1 Y or N I 3
availability location
Pathways
Pathways, also referred to as footpaths, are a public way that is reserved for the movement of pedestrians, motorised wheel chairs and personal mobility
scooters.
Polyline Assets
Point Assets
An area set aside for the purpose of allowing pathway users to cross the road, typically connecting to a pathway on the other side.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Local name path_name Local name of the pathway A 100 L 1
[Link] BaseDepth path_b_dep Depth of the base course 100 I 3 mm D 1
material in millimetres (mm)
[Link] BaseType path_b_typ Type of the base course A 100 Code List 9.26 D 1
material
[Link] Depth Crossing path_c_dep Depth of surface material 150 I 3 D 1
(concrete) for the crossing in
millimetres
[Link] Depth Pathway path_dep Depth of the pathway seal in 100 I 3 D 1
millimetres
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Number of steps path_steps Number of steps within the I 3 D 1
section
[Link] Rail type path_r_typ Rail type associated with Top rail with A 30 D 1
steps wire rope
[Link] Pathway is path_reo The Pathway is reinforced Y - Yes B 1 Y or N D 1
reinforced
[Link] Sub base depth path_s_dep Depth of the sub-base course I 3 mm D 1
material in millimetres (mm)
[Link] Sub base type path_s_typ Type of the sub-base course A 100 Code List 9.26 D 1
material.
As per VicRoads Standard
Specification
[Link] Width path_wid If the segment is a set of DC 3 2 m D 1
stairs with irregular width, an
average width is to be
included.
[Link] Obstruction type path_obst Obstruction type that will Locked gate A 250 D 2
impede the pathway
[Link] Rail material path_r_mat Material of rail associated with Wood A 30 D 2
steps.
[Link] Crossing cross_mat The material the asset is CONC - A 30 Code List 9.26 D 3
Material constructed of Concrete
[Link] Crossing Type cross_type Identifies the type of pathway Bevelled A 30 D 3
crossing
[Link] Crossing width cross_wdth Width of the crossing in DC 3 2 m D 3
metres
[Link] Length pathway path_len Length of the pathway in DC 4 2 m D 3
metres
[Link] Material Pathway path_mat Pathway material CONC - A 100 Code List 9.26 D 3
Concrete
[Link] Pathway type path_typ Pathway Type Beach Access A 100 Code List 9.28 D 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Treatment path_treat Treatment of the pathway Resurfacing A 100 Code List 9.60 P 2
[Link] Instruction path_instr Instructions for getting round The contact AN 250 I 3
an obstruction such as a details of the
locked gate or barrier on a person with a
pathway gate key
Pavement
The portion of a road (typically granular layers) placed above the design subgrade level for the support of vehicular traffic, and upon which the pavement
surface (wearing course) is applied.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
General
[Link] Lateral width left p_wid_l Lateral distance measured DC 5 2 m L 1
from the road centreline to
the left side of the formed
pavement. Side is determined
by the direction of increasing
distance along the link
[Link] Lateral width p_wid_r Lateral distance measured DC 5 2 m L 1
right from the road centreline to
the right side of the formed
pavement. Side is determined
by the direction of increasing
distance along the link
[Link] Chainage at road_from Chainage at start of street I 6 m L 1 M
start of street segment. ‘SLK_from’ is for
segment WA members and
‘Road_from’ is for other
jurisdictions. This is to be the
starting chainage of the
centreline. Chainage is to
correspond with the
pavement length
[Link] Chainage at end road_to Chainage at end of street I 6 L 1 M
of street segment. ‘SLK_to’ is for WA
segment members and ‘Road_to’ is for
other jurisdictions. The
finishing chainage of the
centreline.
[Link] Centreline seg_cl_len Centreline segment length DC 4 2 m D 1
segment length between chainages in metres
[Link] Material Source mat_source The originating source of the Quarry A 50 D 2
material
[Link] Material Source mat_s_name The name of the originating Winstones A 50 D 2
Name source of the material
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Recycled p_recy_per The percentage of recycled 15 I 3 % D 2
Percentage material used in the
pavement construction
[Link] Recylced p_recy_mat The name of the recycled Winstones A 50 D 2
Material material used in the
pavement construction
[Link] Design ESA design_esa Design equivalent standard 1.5 DC 2 1 MESA P 2
axles used in the pavement
design, in millions (1x106)
[Link] Load Limit p_axle_max Maximim axle load in tonnes. 1.5 DC 2 1 tonne P 2
Pavement Layers
[Link] Layer depth p_lay_dep Depth of material for the layer I 3 mm D 1
[Link] Layer material p_lay_mat Type of material for the layer A 100 Code List 9.26 D 1
[Link] Layer number p_lay_no The order of the pavement A 2 D 1
layers from top (layer 1) to
bottom. The layer number
has the youngest layer at top
(top layer), with the oldest at
the bottom
[Link] Layer Stabilising p_lay_stab Stabilizing agent used in the A 30 D 1
agent layer
[Link] Stabilising agent p_stab_pct Stabilizing agent percentage I 2 D 1
percent in the layer
[Link] Layer type p_lay_typ The type of layer the A 1 S - Subgrade D 1
information relates to. This can L - Pavement
be either the subgrade or a layer
pavement layer
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] layer CBR p_lay_cbr Californian Bearing Ratio DC 5 2 P 2
(CBR) for the natural ground
and granular (non-modified)
layer
[Link] layer UCS p_lay_ucs Unconfined compressive DC 3 2 Mpa P 2
strength (UCS) for a modified
granular or bound layer,
including subgrades
Pavement Surfacing
The part of the pavement upon which the traffic travels, that is specifically designed to resist abrasion from traffic and to minimise the entry of water.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
General
[Link] Lateral width left s_wid_l Lateral distance measured DC 5 2 m L 1
from the road centreline to the
left side of the pavement
surfacing. Side is determined
by the direction of increasing
distance along the link
[Link] Lateral width s_wid_r Lateral distance measured DC 5 2 m L 1
right from the road centreline to the
right side of the formed
pavement. Side is determined
by the direction of increasing
distance along the link
[Link] Length of seal seal_len The length of seal for the I 5 m D 1
layer
[Link] Width of seal seal_wid Width of the seal layer. The DC 6 2 D 1
seal width is only required for
a partial width seal, and will
have an offset from the
centreline
[Link] Road surface psurf_stat The status of the current S, U A 1 D 1 NM
status surfacing type.
[Link] Year of current seal_year The calendar year of the most I 2 Yr D 1 M
surface installation recent surfacing.
[Link] Seal specification seal_spec The specification covering the P17 AN 30 P17 I 3
way the contract is managed P4
and warranted
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Surrfacing Detail
[Link] Smallest chip chip_small The smallest chip size for a Two Chip 3,5 I 2 D 1
size two chip seal seal, the
smallest chip
size is 5
[Link] Largest Chip chip_large The largest chip size for a two Two Chip 3,5 I 2 D 1
chip seal seal, the
largest chip
size is 3
[Link] Depth of the seal s_dep The depth of the seal in I 3 D 1
millimetres. This is used for
non-chip seal surfaces that
have a depth such as slurry,
concrete, and asphaltic
concrete. Chip seals have a
depth of 0
[Link] Seal layer s_func Function of the seal layer M- A 30 Code List 9.59 D 1
function Membrane
[Link] Surfacing s_mat A description of the material A 30 D 1 M
material type type of the surfacing layer
[Link] The surface layer s_lay_no The surface layer number. A 1 1 to 99 D 1
number
[Link] Polished Stone psv Polished Stone Value of Chip I 2 50 to 65 P 2
Value of Chip for for the seal layer
the seal layer
[Link] Additive quantity s_add_quan Additive Quantity used in the I 3 0 to 100 I 3
seal (pph)
[Link] Type of additive s_add_typ Type of additive used in the A 4 Code List 9.56 I 3
seal
[Link] Adhesion agent s_adh_quan Quantity of Adhesion agent 5 I 3 % 0 to 100 I 3
quantity used in the seal (pph)
[Link] Adhesion agent s_add_typ Adhesion agent used in the A 30 Code List 9.57 I 3
seal
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Average Least s_ald Average Least Dimension of DC 4 2 mm 0 to 20 I 3
Dimension the chip
[Link] Binder s_bind_rat Binder application rate of the 2.3 DC 6 2 I 3
application rate seal (litres per square metre)
[Link] Binder type s_bind_typ Binder type of used in the A 30 Code List 9.58 I 3
seal
[Link] Cutter Quantity s_cut Cutter Quantity used in the I 2 % 0 to 20 I 3
seal (pph)
[Link] Cutter type s_cut_typ Cutter type used in the seal A 30 I 3
[Link] Elastic recovery s_elas_rec Elastic recovery of the 15 I 3 % 0 to100 I 3
polymer modified seal. This
information has to be
obtained from the polymer
modified asphalt cement
provider as it is specific to the
mix. Applicable to polymer
modified mixes only. This is
different to torsional recovery
and should not be confused.
Specified as a percent
[Link] Quantity of flux s_flux Quantity of flux used in the I 3 0 to 10 I 3
seal (pph)
[Link] Polymer s_poly Polymer percentage in the I 3 0 to 50 I 3
percentage seal layer
[Link] Polymer type s_ply_typ Polymer type in the seal layer AN 100 I 3
[Link] Percentage of s_recy_mat Percentage of recycle I 3 0 to 100 I 3
recycle material material in the seal layer
[Link] Recycled s_recy Recycled component in the A 10 Code List 9.26 I 3
component seal layer
[Link] Binder softening s_bind_sp Softening point of the binder I 3 I 3
point used in seal layer (degrees
Celsius)
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Quarry source s_source The name of the Quarry the A 30 I 3
aggregate used for chip
sealing or asphalt mix was
sourced from
Pits
Includes assets referred to as catch pit, sumps and Manhole chambers. Catch pits/ sumps are a concrete pit at the end of a water channel used to settle out
solids before the water flow enters a pipe drain. A hole or depression into which water is drained.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] X Coordinate pit_x X Coordinate locator point in DC 9 2 L 2
metres. Will be used in the
check of pipe endpoints
compared to pit locator points
[Link] Y Coordinate pit_y Y Coordinate locator point in DC 9 2 L 2
metres. Will be used in the
check of pipe endpoints
compared to pit locator points
[Link] Diameter width pit_dia Side width of pit or diameter if 600 I 4 mm D 1
circular
[Link] Length pit_len Side length of pit if not circular 900 I 3 m D 1
[Link] Lid Type pit_li_typ Pit lid type Grate A 40 Code List 9.33 D 1
[Link] Pit number pit_no Unique number in this 39A AN 15 D 1
Subdivision or Project Stage
[Link] Type pit_typ Type of pit Twin A 100 D 1
[Link] Litter trap type pit_trap Type of litter trap Sand Trap A 20 Code List 9.34 D 2
[Link] Depth pit_dep Natural or Finished Surface 1.27 DC 3 2 D 3
level to invert of outlet pipe in
metres
[Link] Fence present pit_fence Existence of a fence around Y - Yes B 1 Y or N D 3
the asset
[Link] Finished surface pit_level Cover Level Metres - Finished DC 7 2 D 3
level Surface Level (FSL) of pit
[Link] Number of step pit_steps Number of step irons. If no 4 I 2 D 3
irons step irons enter “0”
[Link] Construction pit_st_typ Construction Type Insitu A 6 Code List 9.32 I 3
Type
Poles
These are poles onto which other assets are connected such as traffic signal, street lights, CCTV cameras etc.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Pole height pole_hei Pole height from the ground 7.6 DC 4 2 m D 1
surface
[Link] Pole Material pole_mat Pole Material type CONC - A 10 Code List 9.26 D 1
Concrete
[Link] Pole type pole_typ Pole type A 30 D 1
[Link] Pole earth pole_earth Method used to earth the pole A 30 D 2
method
[Link] Foundation pofoun_mat Foundation material of the CONC - A 100 D 2
material pole Concrete
[Link] Foundation type pole_found Foundation type of the pole A 30 D 2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Pole controller pole_cntrl Pole controller type Time A 30 D 2
[Link] Pole finish pole_finsh Pole finish Powder A 30 D 2
Coated
[Link] Pole attachments pole_attac Pole attachments are present Y - Yes B 1 Y or N I 3
present
[Link] Pole pole_manuf Pole manufacturer. Jones A 100 I 3
Manufacturer Manufacturing
[Link] Pole model pole_model Pole model number. J1234 AN 20 I 3
number
[Link] Design Standard pole_stand Design Standard for the pole A 30 I 3
Public Art
Public art or memorials that require maintenance and form part of the asset register.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Description of art_desc Description of Artwork. Statue of A 100 D 1
Artwork Child
[Link] Artwork material art_mat Artwork material. Brass A 100 Code List 9.26 D 1
[Link] Type art_type Type of artwork or memorial Statue, A 100 D 1
Memorial
[Link] Plaque plaque_des Plaque description on the art AN 250 D 3
description work or memorial
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Electrical elec_cert Electrical Certification AN 50 I 3
Certification (where artwork is electrical or has
(where artwork is lighting). ONLY needs to be
electrical or has populated in the event that the
lighting) Artwork is electrical or lighting is
required.
A certificate is required after
working on an electrical
installation and connecting it to a
source of electricity by the person
for whom the work was done.
Public Toilets
Public toilet or ablution blocks that contain toilets, and /or changing and washing facilities.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Changing wc_change If the Public Toilet contains Y - Yes B 1 Y or N D 2
facilities present changing facilities
[Link] Floor material wc_flo_mat Floor material Tiles, A 100 D 2
Concrete
[Link] Number of wc_fem_shw Number of Female Shower 2 I 2 D 2
female showers Facilities
[Link] Number of male wc_mal_shw Number of Male Shower 2 I 2 D 2
showers Facilities
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Number of male wc_mal_uri Number of Male Urinal 4 I 2 D 3
urinal fixtures Fixtures
[Link] Number of male wc_mal_fix Number of Male WC Fixtures 2 I 2 D 3
WC fixtures
[Link] Sharp disposal wc_sharps If the Public Toilet contains Y - Yes B 1 Y or N D 3
present Sharp Disposal Facilities
[Link] Waste water wc_waste The waste water disposal Town Sewer A 20 D 3
disposal method or Septic Tank
[Link] Toilet partition wc_par_mat Toilet Partition Material Wood A 20 Code List 9.26 I 3
material
Retaining Walls
A wall constructed to resist lateral pressure from the adjoining ground or to maintain in position a mass of earth. These can be for pavement, pathways,
natural/cut slope protection, fore shore protection and around bridge abutments.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Lateral offset rw_offset Lateral offset in metres from DC 3 1 m L 1
face the road centreline to the
asset face, at the asset start
point, from the increasing
direction of travel
[Link] Length of rw_len Length of the retaining wall DC 4 2 m D 1
retaining wall
[Link] Restraining rw_restrai Restraining mechanism of the Gravity A 30 Code List D 1
mechanism of asset 9.41
the asset
[Link] Structure type struc_typ Structure type Gabion A 30 Code List D 1
Basket, Sea 9.42
Wall
[Link] Average height avg_hei Average height of the asset in 5.3 DC 3 1 m D 2
metres (m)
[Link] Drainage drainage Drainage mechanism P - Porous A 30 Code List 9.14 D 2
mechanism
[Link] Face area of wall rw_fac_are Face area of the wall in 25.16 DC 6 2 sq.m D 2
square metres (m2)
[Link] Face material rw_fac_mat Wall face material Brick A 30 Code List D 2
9.26
[Link] Foundation type found_typ Foundation type A 30 D 2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Features above rw_above Features above the wall Bank A 30 Code List 9.1 I 3
the wall
[Link] Back tilt angle rw_tilt Back tilt angle measured from 10° I 2 I 3
the vertical
[Link] Features below rw_below Features below the wall SEA A 30 Code List 9.1 I 3
the wall
[Link] Face thickness rw_fac_thi Face thickness of the wall in 150 I 4 mm I 3
millimetres (mm)
Road Barriers
Provides protection from errant vehicles/ road users for safety purposes. They are designed to allow for vehicles to be deflected to safety from a hazard. They
are used to separate opposing traffic flows, and also as protection from hazards.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Lateral offset rb_offset Lateral offset in metres from DC 3 1 m L 1
face the road centreline to the
asset face, at the asset start
point, from the increasing
direction of travel
[Link] Length of barrier rb_len Length of the road barrier in 125.68 DC 5 2 m D 1
metres
[Link] Material barrier rb_rai_mat Material of the road barrier rail Steel A 100 Code List 9.26 D 1
rail.
[Link] Road barrier type rb_typ Road barrier type Noise A 100 Code List 9.43 D 1
Attenuation
[Link] Height of barrier rb_hei Height of the road barrier 650 I 4 mm D 2
measured from the ground
surface
[Link] Material barrier rb_pos_mat Material of barrier posts Wood A 100 Code List 9.26 D 2
posts
[Link] Attachments on rb_attach Attachments on the barrier reflectorised A 30 D 2
the barrier discs
[Link] Rail width rb_wid Rail width 200 I 4 mm D 2
[Link] Barrier End style rb_end_typ End style type of the barrier A 30 D 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
[Link] Coating system coat_sys Coating system A 30 I 2
Shelters
A structure that provides weather protection to various road users. It can include cycle, bus and pedestrian shelters.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Shelter type sh_typ Shelter type. Pedestrian, A 100 Code List 9.46 D 1
Bus, Tram
etc.
[Link] Disabled access sh_dis_acc Disabled access availability. Y - Yes B 1 Y or N D 2
available
[Link] Floor material sh_flr_mat Floor material A 100 Code List 9.26 D 2
[Link] Roof material sh_roo_mat Roof material A 100 Code List 9.26 D 2
[Link] Wall material sh_wal_mat Wall material A 100 Code List 9.26 D 2
[Link] Seating material seat_mat Seating material in the bus Plastic A 100 Code List 9.26 D 3
shelter.
[Link] Advertising on advert If there is any advertising Y - Yes B 1 Y or N I 3
shelter displayed on the shelter.
[Link] Shelter sh_manuf Shelter manufacturer A 100 I 3
manufacturer
[Link] Model number of sh_model Model number of Shelter AN 20 I 3
shelter
Signs
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 road
users. They may or may not be illuminated.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Sign Type sign_typ Sign type. Refer to Australian A 100 D 1
Standards or MOTSAM (NZ)
[Link] Ground height sign_hei Height from ground to bottom DC 3 1 m D 2
of the sign panel
[Link] Sign height sign_hei Total height of the sign 1200 I 4 mm D 2
[Link] Number of posts sign_posts Number of sign posts 2 I 2 D 2
[Link] Post Material sign_p_mat Material of the sign post Wood A 100 D 2
[Link] Width of sign sign_wid Total width of the sign 500 I 4 mm D 2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Frame material sign_frame Sign frame material A 30 D 3
[Link] Number of sign sign_panel Number of panels in the sign 4 I 2 D 3
panels
[Link] Strengthening sign_stren Whether there’s a Y - Yes B 1 Y or N D 3
bar present strengthening bar
[Link] Background sign_bcol Background colour A 30 I 2
colour
[Link] Background sign_b_mat Background material A 30 I 2
material
[Link] Wording on sign sign_words Wording on the sign or if A 250 I 1
there are no words, a
description of the sign
[Link] Legend colour sign_wordc Legend colour A 30 I 2
[Link] Legend material sign_wordm Legend material A 30 I 2
[Link] Sign sign_manuf Sign manufacturer A 100 I 3
manufacturer
[Link] Sign angle sign_angle Orientation of the sign. Angle 225 I 3 Degrees I 2
from North, clockwise to the
bracket (its bearing).
[Link] Panel material sign_mat Material of the sign panel Aluminium A 100 I 1
[Link] Australian sign_refsd Australian Standard AN 100 I 3
Standard Reference
Reference
[Link] Local Sign sign_refno Standard Local Sign AN 100 I 3
Reference Reference Number.
Number
[Link] Support type sign_supp Support type of the sign On a post A 100 I 2
Slopes
Slope assets include the natural and mechanical treatment to either stabilise slopes or to control the degradation of slopes.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Area of slope slope_area The area obtained from plans, I 6 sq.m D 1
face or accurately measured on
site
[Link] Slope in cut or fill slope_typ Whether the slope was Cut or Fill A 1 C - Cut D 1
created by a cutting (above F- Fill
road slope) or filling activity
(embankment below or above
road slope)
[Link] Gradient of slope_grad Expressed as the rise A 3 % D 1
batter slope (change in height from the
ground to the top of the slope)
over the run (the horizontal
ground distance from the toe
of the slope to where the rise
is measured from), expressed
as a percentage
[Link] Slope length slope_len This is the actual length of the 1020.25 I 5 m D 1
slope measured from the start
point to the end point
[Link] Average height slope_hei This is a weighted average DC 3 1 m D 1
height calculated from [area] /
[length], where area is known
[Link] Planting exists slope_plan Planting exists to stabilise the N - No B 1 Y or N D 1
slope
[Link] Slope is slope_rein The Bank is reinforced N - No B 1 Y or N D 1
reinforced
[Link] Active or passive slope_drn The type of drainage utilised. Active or A 1 A - Active D 2
drainage Active where the drainage is Passive P - Passive
assisted by pumping or other
means, or is passive by way
of natural gravity
[Link] Vegetation type veg_typ Vegetation Type planted A 30 Code List 9.55 D 2
planted
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Type of anchors anchor_typ Type of anchors used for the A 30 Code List 9.49 I 2
stabilising material if not
vegetated
[Link] Type of drainage dr_liner The type of drainage liner Impermeable A 30 Code List 9.50 I 3
liner utilised
[Link] Bank foundation found_mat The foundation material of the A 30 Code List 9.52 I 2
material Bank
[Link] Geotextile Fabric geotextile Geotextile Fabric used A 30 Code List 9.51 I 2
used
[Link] Geotechnical slope_mon Geotechnical monitoring A 50 Code List 9.53 I 2
monitoring equipment used for slopes
equipment
[Link] Slope seismic slope_seis The seismic rating for the A 2 Code List 9.54 I 3
rating slope
[Link] Standpipe standpipe Has a standpipe been Y - Yes B 1 Y or N I 3
installed installed to monitor ground
water levels
Structures
Assets included under structures are sign gantries, and others that are not defined elsewhere. Bridges have their own asset group so are not included here.
L1
End of asset section Linear distance along road centreline /
spatial
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Structure height struc_hei Structure height DC 5 2 m D 1
[Link] Structure struc_mat Material of the structure A 100 Code List 9.26 D 1
material
[Link] Structure type struc_typ Structure type Cantilever A 100 D 1
[Link] Structure width struc_wid Structure width DC 5 2 m D 1
[Link] Structure surface struc_fin Structure finish Paint Finish A 30 D 2
finish
[Link] Foundation found_mat Foundation material A 100 D 2
material
[Link] Structure struc_ftyp Foundation type of the A 30 D 2
foundation type structure
[Link] Structure number struct_sup Number of supports on the I 2 D 2
of supports structure
[Link] Structure struc_att Attachments on the structure Sign, Light A 30 I 3
attachments
[Link] Structure struc_manu Structure manufacturer A 100 I 3
manufacturer
Table Drains
A longitudinal drain, parallel to the road, which conveys surface water run-off from the road to outlet drains. It is an unsurfaced alternative to a kerb and
channel system typically used in a residential street.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Table drain drn_len Length of the table drain in 30.25 DC 5 2 m D 1
length metres
[Link] Table drain drn_dep Average depth of the table 1.05 DC 3 1 m D 2
depth drain in metres measured
from ground level to invert of
the drain
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Table drain drn_mat The material the table drain is Earth A 100 Code List 9.26 D 2
material constructed of
[Link] Table drain drn_shape The general shape of the V shaped, A 100 D 2
shape table drain trapezoidal
[Link] Table drain width drn_wid Average width of the table 2.25 DC 4 2 m D 2
drain measured at ground
level
[Link] Authority drn_resp The name of the responsible A 100 I 3
responsible for Authority for maintenance
maintenance purposes.
Tactile Paving
Tactile pavers used on approaches to pedestrian crossing point to aid visually impaired persons to a safe crossing point.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Tactile paving pav_typ The type of tactile paver that Tiles, Blocks A 100 Code List 9.28 D 2
type has been used
[Link] Number of pav_tiles The number of each tactile 20 I 2 D 3
paving tiles paver type present at the
location
Point Assets
Traffic management devices that manage and control and flow or speed or vehicles/ road users. It includes width restrictions, speed humps/ platforms,
pedestrian crossings, roundabouts and splitter islands. A point asset is defined by a point and has not length (i.e. bollards).
Polygon Assets
Traffic management devices that manage and control and flow or speed or vehicles/ road users. It includes width restrictions, speed humps/ platforms,
pedestrian crossings, roundabouts and splitter islands. A polygon asset has a defined shape and area such as an island.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Point
[Link] Traffic tm_mat The material the traffic Steel A 100 Code List 9.26 D 1
Management management point is
Point Material constructed of
[Link] Traffic tm_p_typ The type of point traffic Bollard A 100 Code List 9.62 D 1
Management management device
Point Type
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Company name tm_manuf The manufacturing company Lunds Pty Ltd A 100 I 3
only for the point traffic
management device
[Link] Model number tm_model The model number for the JK-011-S AN 30 I 3
point traffic management
device
Polygon
[Link] Traffic tm_mat Material of the feature. Rubber A 100 Code List 9.26 D 1
management If the feature is a roundabout,
device material include material of Annulus
(external area of the
roundabout) here.
[Link] Traffic tm_typ Traffic Management device RBT A 100 Code List 9.62 D 1
management type.
device type
[Link] Diameter of tm_is_dia Diameter of the roundabout in 1.05 I 3 m D 2
roundabout metres
[Link] Traffic tm_in_mat The material of the infill of the Grass A 100 D 2
Management asset. This field is only to be
device infill completed if TYPE is a
material Roundabout or the asset has
an infill
[Link] Traffic kerb_typ The type of kerb A 100 Code List 9.22 D 2
management
device kerb type
Traffic Signals
Traffic signals includes all the components of the signal, but not the pole, as this is included in poles. Components include pedestrian call boxes, target
boards, lanterns, controllers etc.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Signal pole ts_pole_id The pole number assigned to AB1234 AN 30 L 1
number the traffic signal pole in
accordance with traffic signal
design. Pole numbering goes
clockwise around the
intersection from the signal
control box
[Link] Site name for the ts_site The site name that is allocated Browns/ John A 30 L 1
signals to the signal set Intersection
[Link] Signal unique ts_unqi_id The unique asset ID allocated AD1234 AN 30 L 1
asset ID to the signal asset
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Controller ID ts_cont_id The Controller ID assigned to 123-346- AN 30 D 1
the signals 125435
[Link] Control system ts_cs_typ Control system type A 30 D 2
type
[Link] Ground height to signal_hei Height from the ground DC 5 2 m D 2
bottom of signal surface to the bottom of the
signal target board
[Link] Signal type ts_sig_typ Signal type A 100 D 2
[Link] Pedestrian call cbox_typ Pedestrian call box type A 30 D 3
box type
[Link] Data logger ts_dat_log Whether there’s a data logger Y - Yes B 1 Y or N D 3
present present
[Link] Earthing type for ts_eth_typ Earthing type for the traffic A 30 D 3
signal pole signal pole
[Link] Luminaire size ts_lum_siz Luminaire size of the signal 200 I 3 mm 200, 300 D 3
aspects. This is generally 200
or 300mm
[Link] Luminaire type ts_lum_typ Luminaire type A 100 D 3
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Defects liability ts_dl_sta Start date of defects liability ddmmyyyy D 8 P 2
start date period
[Link] Maintenance ts_mainreq Maintenance requirements A 100 P 2
requirements
[Link] Signal ts_maintco Name of the company who A 250 P 2
maintenance maintains the signals
company
[Link] Purchase cost purch_cost The overall cost paid at time 180000 Mo 10 2 $ P 2
of installation, or the vested
cost through subdivision
[Link] Purchase date ts_purchda The purchase date for the ddmmyyyy D 8 P 2
signal installation, or vested
date through subdivision
[Link] Access to asset ts_access Access to asset A 30 I 3
[Link] Attachments type ts_attach The attachment type to the Banner Arms A 30 I 3
present on the signal pole
poles
[Link] Manufacturer of ts_make Manufacturer of the call box AN 30 I 3
call box
[Link] Call box model ts_cbmodel Call box model number AN 30 I 3
number
[Link] Luminaire ts_lum_man Luminaire manufacturer A 100 I 3
manufacturer
[Link] Manufacturer of ts_maunf Manufacturer of the signal A 100 I 3
the signal
[Link] Model number ts_model Model number MN12453 AN 30 I 3
[Link] Mounting type ts_mnt_typ Mounting type A 30 I 3
[Link] Signal connected smart_pad The signal is connected to a Y - Yes B 1 Y or N I 3
to a smart pad smart pad
[Link] Signal supplier ts_supp The traffic signal supplier TSL A 30 I 3
[Link] Video detection video_det If video detection is present at Y - Yes B 1 Y or N I 3
present this signal installation
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Visor type visor_type Visor type A 30 I 3
[Link] Warranty end ts_war_end Warranty end date for the ddmmyyyy D 8 I 3
date traffic signal installation
Trees
The location of planted trees, planting method as well as botanical identification. They can be within the berm, or special landscaped areas.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Diameter of trunk tree_dia Diameter of the trunk at DC 4 2 m D 2
breast height (in metres)
[Link] Height at capture tree_hei Height of the tree at the time DC 5 2 m Code List 9.65 D 2
of data capture
[Link] Genus tree_genus Genus of the tree A 30 D 3
[Link] Tree guards tree_guard Tree/ Plant guards are Y - Yes B 1 Y or N D 3
present present
[Link] Stock type tree_stock Stock type of the tree AN 50 D 3
[Link] Tree Age tree_age Age of the tree at time of A 2 Code List 9.63 P 2
capture
[Link] Tree Endemic tree_stat Endemic status of the tree New Zealand AN 100 P 2
status native, exotic
[Link] Maintenance tree_maint Maintenance Seasonal A 250 P 2
requirements issues/requirements fruiting
[Link] Tree tree_sig If the tree has any special Historical A 100 Code List 9.67 P 2
significance significance, or status
[Link] Pruning time tree_prune Time period between pruning I 2 mth P 3
interval cycles
[Link] Common name tree_commo Common Name River Red A 100 I 3
Gums
[Link] Tree Planting tree_metho Planting method for the tree Remnant A 100 Code List 9.66 I 3
method
[Link] Tree tree_roots The environment the tree is Tree Pit A 100 Code List 9.64 I 3
environment for planted into and if it will be
roots root constrained
[Link] Tree species tree_speci Tree Species Eucalyptus A 100 I 2
Camaldulensis
[Link] Support type for tree_supp Support type of the tree One post A 100 I 3
tree
[Link] Overhead wires tree_wires Overhead wires are present Y - Yes B 1 Y or N I 2
present within the trees envelope
Tunnels
A tunnel is an underground roadway, dug through the surrounding soil and enclosed except for the entrance and exit. The physical details of the tunnel are
described here with any mechanical and electrical components recorded under that asset group, and the same for lighting and any ITS assets. Details are
recorded for various components including the portal, buttress, capping beam and barrel.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Left Tunnel tun_wid_l Lateral measurement from the DC 4 2 m L 1 M
Width road centreline to the left
inside edge of the barrel. Left
side is defined from the road
origin, travelling in the
increasing direction.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Right Tunnel tun_wid_r Lateral measurement from the DC 5 2 m L 1 M
Width road centreline to the right
inside edge of the barrel.
Right side is defined from the
road origin, travelling in the
increasing direction.
[Link] Tunnel length tun_len Length of the tunnel measured DC 5 2 m L 1 NM
along the centreline of the
tunnel.
[Link] Tunnel services tun_serv An indication of whether the A 1 L 1 NM
tunnel includes services
(lighting, extraction,
communications, etc.) or is
simply an unserviced tunnel.
[Link] Earthquake eq_rating The earthquake rating for the DC 6 2 D 1
Rating tunnel
[Link] Maximum tun_mx_hei This is the maximum DC 3 1 m D 1 M
trafficable height trafficable height that can
pass through the tunnel,
providing for an "as of right"
width envelope. It may require
a lane closure to allow
passage down the centre of
the tunnel. The high is
measured from the road
surface to the point that
provides the "as of right"
width dimension
[Link] Tunnel tun_clear The height measured from the DC 6 2 D 1
Clearance road surface, at the outside
edge of the traffic lane, to the
inside surface of the barrel.
This is the maximum height
that can pass while staying
within the traffic lane.
Consideration will also need
to be given if lower
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
restrictions are present within
the tunnel
[Link] Tunnel Function tun_func The function the tunnel PED - A 100 Code List 9.68 D 1
provides whether it be for the Pedestrian
passage of pedestrians, underpass
vehicles, rail, bicycles, or a
combination of road users
[Link] Tunnel Structure tun_st_typ A category for the different UND - A 100 Code List 9.69 D 1
Type types of tunnels Underpass
[Link] Barrel height tun_ba_hei Height of the tunnel measured DC 5 2 m D 2
from the road surface to the
highest point on the inside of
the barrel
[Link] Barrel material tun_ba_mat The material that the barrel in CONC - A 30 D 2
constructed of. Concrete
[Link] Barrel surface tun_ba_typ The type of surface treatment paint A 30 D 2
treatment type that exists on the barrel
[Link] Barrel thickness tun_ba_thi The thickness of the I 4 mm D 2
constructed barrel. This is
measured as the thickness
from the tunnel cut face to the
inside finished surface
[Link] Barrel width tun_ba_wid Measured at the road surface DC 5 2 m D 2
and is the inside width of the
barrel
[Link] Buttress height tun_bu_hei Measured from the road DC 5 2 m D 2
surface to the underside of the
capping beam. This is recorded
as the average height for
multiple variable heights.
[Link] Buttress material tun_bu_mat The material the buttress is Wood A 30 D 2
constructed of
[Link] Capping beam tun_ca_mat The material the capping CONC - A 30 D 2
material beam is constructed of Concrete
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Number of tun_e_exit The number of all emergency I 2 # D 2
emergency exits exits within the length of the
tunnel. This includes vehicular
and pedestrian
Vehicle Crossings
These are a formed area where vehicles are permitted to cross over channel and footpath. The exact extend of this defined area varies between jurisdictions.
Vehicle crossing construction and type can vary depending on its use (i.e. residential, commercial, industrial etc.).
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Vehicle crossing cross_mat The finished surface material CONC - A 100 Code List D 1
material of the vehicle crossing Concrete 9.26
[Link] Vehicle crossing cross_typ The constructed type of Residential, A 100 Code List D 1
type vehicle crossing commercial, 9.28
industrial etc.
[Link] Vehicle crossing cross_dep The constructed depth of the 150 I 3 mm D 2
depth finished surface for the
vehicle crossing
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
[Link] Vehicle crossing cross_reo Reinforcing mesh has been Y - Yes B 1 Y or N D 2
reinforcing mesh used in the construction of the
present vehicle crossing. This could
be specified in an
organisations construction
standards
[Link] Vehicle crossing cross_wid Width of the vehicle crossing 3 DC 3 1 m D 2
width excluding in metres excluding the
splays splays. Measured at the road
reserve boundary
[Link] Vehicle crossing crs_b_dep Depth of the base course 100 I 3 mm D 3
basecourse material
depth
[Link] Vehicle crossing crs_b_typ Type of the base course A 100 Code List D 3
base course type material 9.26
[Link] Vehicle crossing crs_s_dep Depth of the sub-base course 0 I 3 mm D 3
subbase course material
depth
[Link] Vehicle crossing crs_s_typ Type of the sub-base course A 100 Code List D 3
subbase course material. 9.26
type
8.4 Condition
Overview
Condition data describes asset information that relates to either its functional performance or where it sits in its lifecycle. Understanding condition data is
fundamental to many asset management practices including planning, valuation and predictive modelling. Condition data will often interact with other pieces of
data to inform items such as access, performance, risk, works and costs.
The items listed below are considered core to road management. If collected, they should be able to be reported in this way to allow easy comparison. It is in
no way intended to be a definitive list of all data items, nor is it intended to restrict the collection of additional items. It is acknowledged that advances in
technology may warrant changes to this list.
Scope
There are many methods of assessing condition which are often intended to fit a specific business, operational or management requirement. Collection
standards can also be driven by historical or technological restrictions. This data standard outlines three levels of sophistication (Soph) which can be applied
to the method of how the data is collected.
The assessment is done subjectively with no relation to any standard or measurement. This is often just a simple visual inspection with the reporting being a
discrete variable ranging from “as new” to “end of life”.
The assessment is still done subjectively but made in relation to a standard, guideline or measurement. The use of a standard, guideline or measurement is
to try add some portability, comparability and reliability to the data. The measurement is often an estimate taken visually, or an overall score extrapolated from
descriptive words and pictures.
The assessment is typically a scientific measure as defined by a specified test method, such as the Austroads Test Methods. This includes automated
parameters such as roughness, rutting and texture.
It is understood that there are items that fall between these levels of sophistication. Generally, the higher the level of sophistication, the higher the level of
accuracy, although this may differ depending on each situation. Where appropriate, a reference has been given to the most relevant standard for further
details about that data item. Many data items are covered in detail under the Austroads Guide to Asset Management.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Subjective
8.4.1 Subjective cond_subj A numerical rating, established I 1 Code List 9.7 P 1
condition by desktop judgement, that
represents the current
condition of an asset in
meeting its defined service
objectives
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Climate
8.4.11 Thornthwaite clim_tmi Thornthwaite Moisture Index I 3 Typically -60 P 3
Moisture Index to 200
Pavement Cracking
8.4.12 All cracking cr_all_ex The percentage affected I 3 % P 3 AGAM05E- M
extent area of a 100m section 06
where lcracking is evident in
the traffic lane
8.4.13 All cracking cr_all_sv Average width of the I 1 mm P 3 AGAM05E-
severity cracking over the 100m 06
section
8.4.14 Longitudinal cr_long_ex The percentage affected I 3 % P 3 AGAM05E-
cracking extent area of a 100m section 06
where longitudinal cracking is
evident in the traffic lane
8.4.15 Longitudinal cr_long_sv Average width of the I 1 mm P 3 AGAM05E-
cracking severity longitudinal cracking over the 06
100m section
8.4.16 Transverse cr_tran_sv The percentage affected I 3 % P 3 AGAM05E-
cracking extent area of a 100m section 06
where transverse cracking is
evident in the traffic lane
8.4.17 Transverse cr_tran_ex Average width of the I 1 mm P 3 AGAM05E-
cracking severity transverse cracking over the 06
100m section
8.4.18 Crocodile/block cr_croc_sv The percentage affected I 3 % P 3 AGAM05E-
cracking severity area of a 100m section 06
where crocodile cracking is
evident in the traffic lane
8.4.19 Crocodile/block cr_croc_ex Average width of the I 1 mm P 3 AGAM05E-
cracking extent crocodile cracking over the 06
100m section
8.4.20 Cracking survey cr_date Date-time that cracking ddmmyyyy D 8 P 1 M
date-time survey was done
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.21 Cracking survey cr_name Name of operator that AN 20 P 1
operator crackingsurvey was done by
Pavement Deflection
8.4.22 Deflection p_df_veh Type of vehicle used to AN 20 Code List 9.13 P 3 AGAM05D- M
testing vehicle measure deflection 08
8.4.23 Pavement p_df_d0 Pavement deflection at the DC 4 μm P 3 AGAM05D- M
deflection d0 test load. As measured using 08
a Benkelman beam,
deflectograph, falling weight
deflectometer or traffic speed
deflectometer. Not
normalised.
8.4.24 Pavement p_df_d200 Pavement deflection at DC 4 μm P 3 AGAM05D-
deflection d200 200mm from the test load. As 08
measured using a
Benkelman beam,
deflectograph, falling weight
deflectometer or traffic speed
deflectometer. Not
normalised
8.4.25 Pavement p_df_d300 Pavement deflection at DC 4 μm P 3 AGAM05D-
deflection d300 300mm from the test load. As 08
measured using a
Benkelman beam,
deflectograph, falling weight
deflectometer or traffic speed
deflectometer. Not
normalised
8.4.26 Pavement p_df_d900 Pavement deflection at DC 4 μm P 3 AGAM05D-
deflection d900 900mm from the test load. As 08
measured using a
Benkelman beam,
deflectograph, falling weight
deflectometer or traffic speed
deflectometer. Not
normalised
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.27 Pavement p_df_d1500 Pavement deflection at DC 4 μm P 3 AGAM05D-
deflection d1500 900mm from the test load. As 08
measured using a
Benkelman beam,
deflectograph, falling weight
deflectometer or traffic speed
deflectometer. Not
normalised
8.4.28 Actual applied p_df_act Actual applied load for I 3 kN P 3 AGAM05D-
load pavement deflection testing 08
in kN
8.4.29 Ambient air temp_air Ambient air temperature DC 3 1 deg P 3 AGAM05D-
temperature 08
8.4.30 Pavement temp_pave Pavement temperature DC 3 1 deg P 3 AGAM05D-
temperature 08
8.4.31 Deflection p_df_date Date-time that deflection ddmmyyyy D 8 P 1 M
survey date-time survey was done
8.4.32 Deflection p_df_name Name of operator that AN 20 P 1
survey operator deflection survey was done
by
Pavement Roughness
8.4.33 Lane roughness iri_lane Pavement roughness DC 4 2 m/km P 3 AGAM05B- NM
quarter car expressed as Lane IRIqc, 07
reported at 100m intervals
8.4.34 Inner wheel path iri_iwp Pavement roughness DC 4 2 m/km P 3 AGAM05B- M
roughness expressed as IRIqc, reported 07
at 100m intervals
8.4.35 Outer wheel path iri_owp Pavement roughness DC 4 2 m/km P 3 AGAM05B- M
roughness expressed as IRIqc, reported 07
at 100m intervals
8.4.36 Roughness iri_date Date-time that roughness ddmmyyyy D 8 P 1 M
survey date-time survey was done
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.37 Roughness iri_name Name of operator that AN 20 P 1
survey operator roughness survey was done
by
Pavement Rutting
8.4.38 Rut depth lane rut_lane The maximum rut as DC 3 1 mm P 3 AGAM05C-
measured using a 3m 07
straight edge, across both
lanes, and reported at 100m
intervals
8.4.39 Rut depth inner rut_iwp Maximum rut depth inner DC 3 1 mm P 3 AGAM05C- NM
wheel path. Measured using 07
a 2m straight edge, at the
deepest transverse cross
section point, and reported at
100m intervals
8.4.40 Rut depth rut_iwp_sd Pavement rutting in terms of DC 3 1 mm P 3 AGAM05C-
standard standard deviation in the 07
deviation inner inner wheel path. The
standard deviation of the
maximum rut depths
collected over the 100m
section
8.4.41 Rut depth inner rut_iwp_5 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path 0- section where the average 07
<5mm inner wheel path rutting
depth <=5mm
8.4.42 Rut depth inner rut_iwp_10 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>5mm-<10mm inner wheel path rutting
depth >5mm,<=10mm
8.4.43 Rut depth inner rut_iwp_15 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>10mm-<15mm inner wheel path rutting
depth >10mm,<=15mm
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.44 Rut depth inner rut_iwp_20 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >15- section where the average 07
<20mm inner wheel path rutting
depth >15mm,<=20mm
8.4.45 Rut depth inner rut_iwp_25 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >20- section where the average 07
<25mm inner wheel path rutting
depth >20mm, <=25mm
8.4.46 Rut depth inner rut_iwp_30 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >25- section where the average 07
<30mm inner wheel path rutting
depth >25mm, <=30mm
8.4.47 Rut depth inner rut_iwp_35 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >30- section where the average 07
<35mm inner wheel path rutting
depth >30mm, <=35mm
8.4.48 Rut depth inner rut_iwp_40 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >35- section where the average 07
<40mm inner wheel path rutting
depth >35mm, <=40mm
8.4.49 Rut depth inner rut_iwp_X0 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>40mm inner wheel path rutting
depth >40mm
8.4.50 Rut depth outer rut_owp Maximum rut depth outer DC 3 1 mm P 3 AGAM05C- NM
wheel path. Measured using 07
a 2m straight edge, at the
deepest transverse cross
section point, and reported at
100m intervals
8.4.51 Rut depth rut_owp_sd Pavement rutting in terms of DC 3 1 mm P 3 AGAM05C-
standard standard deviation in the left 07
deviation inner wheel path. The standard
deviation of the maximum rut
depths collected over the
100m section
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.52 Rut depth outer rut_owp_5 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path 0- section where the average 07
<5mm outer wheel path rutting
depth <=5mm
8.4.53 Rut depth outer rut_owp_10 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>5mm-<10mm outer wheel path rutting
depth >5mm,<=10mm
8.4.54 Rut depth outer rut_owp_15 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>10mm-<15mm outer wheel path rutting
depth >10mm,<=15mm
8.4.55 Rut depth outer rut_owp_20 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >15- section where the average 07
<20mm outer wheel path rutting
depth >15mm,<=20mm
8.4.56 Rut depth outer rut_owp_25 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >20- section where the average 07
<25mm outer wheel path rutting
depth >20mm, <=25mm
8.4.57 Rut depth outer rut_owp_30 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >25- section where the average 07
<30mm outer wheel path rutting
depth >25mm, <=30mm
8.4.58 Rut depth outer rut_owp_35 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >30- section where the average 07
<35mm outer wheel path rutting
depth >30mm, <=35mm
8.4.59 Rut depth outer rut_owp_40 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path >35- section where the average 07
<40mm outer wheel path rutting
depth >35mm, <=40mm
8.4.60 Rut depth outer rut_owp_X0 The percentage of a 100m I 3 % P 3 AGAM05C-
wheel path section where the average 07
>40mm outer wheel path rutting
depth >40mm
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.61 Rutting survey rut_date Date-time that rutiing survey ddmmyyyy D 8 P 1 M
date-time was done
8.4.62 Rutting survey rut_name Name of operator that rutiing AN 20 P 1
operator survey was done by
Pavement Surface Skid
8.4.63 SCRIM speed sfc_speed Speed of Sideways-force I 3 km/h P 3 AGAM05F-
Coefficient Routine 09
Investigation Machine
(SCRIM) for testing
8.4.64 SCRIM inner sfc_iwp Skid resistance as collect by DC 3 SFC P 3 AGAM05F-
wheel path a Sideways-force Coefficient 09
Routine Investigation
Machine (SCRIM) in the
inner wheel path
8.4.65 SCRIM outer sfc_owp Skid resistance as collect by DC 3 SFC P 3 AGAM05F-
wheel path a Sideways-force Coefficient 09
Routine Investigation
Machine (SCRIM) in the
outer wheel path
8.4.66 SCRIM survey sfc_date Date-time that rutiing survey ddmmyyyy D 8 P 1
time-date was done
8.4.67 SCRIM vehicle sfc_veh Sideways-force Coefficient AN 20 Code List 9.45 P 3 AGAM05F-
Routine Investigation 09
Machine (SCRIM) vehicle
description
8.4.68 Skid Resistance skid_test The Method used to measure AN 10 Code List 9.48 P 3 AGAM05F-
Test the road surface skid 09
resistance.
8.4.69 Skid resistance sk_res_20 Skid resistance as DC 3 2 P 2
20m characterised by the
coefficient of friction. Ratio of
the traction force to the
vertical load averaged over a
20m length
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.70 Skid resistance sk_res_50 Skid resistance as DC 3 2 P 2
50m characterised by the
coefficient of friction. Ratio of
the traction force to the
vertical load averaged over a
50m length
Pavement Surface Texture
8.4.71 SMTD Pavement tx_SMT_iwp Pavement texture Sensor DC 3 1 mm P 3 AGAM05G-
texture inner Measured Texture Depth 09
wheel path (SMTD) measured in the
inner wheel path reported at
100m intervals
8.4.72 SMTD Pavement tx_SMT_owp Pavement texture Sensor DC 3 1 mm P 3 AGAM05G-
texture outer Measured Texture Depth 09
wheel path (SMTD) measured in the
outer wheel path reported at
100m intervals\
8.4.73 SMTD Pavement tx_SMT_bwp Pavement texture Sensor DC 3 1 mm P 3 AGAM05G-
texture between Measured Texture Depth 09
wheel path (SMTD)) between the left
and right wheel paths
reported at 100m intervals
8.4.74 MPD Pavement tx_MPD_iwp Pavement texture Mean DC 3 1 mm P 3 AGAM05G- M
texture inner Profile Depth (MPD) 09
wheel path measured in the inner wheel
path reported at 100m
intervals
8.4.75 MPD Pavement tx_MPD_owp Pavement texture Mean DC 3 1 mm P 3 AGAM05G- M
texture outer Profile Depth (MPD) 09
wheel path measured in the outer wheel
path reported at 100m
intervals\
8.4.76 MPD Pavement tx_MPD_bwp Pavement texture Mean DC 3 1 mm P 3 AGAM05G- M
texture between Profile Depth (MPD) between 09
wheel path the left and right wheel paths
reported at 100m intervals
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.77 Texture survey tx_date Date-time that texture survey ddmmyyyy D 8 P 1 M
date-time was done
8.4.78 Texture survey tx_name Name of operator that texture AN 20 P 1
operator survey was done by
Bridge
8.4.79 Bridge condition br_cond_1 Percent of asset at bridge I 3 % Condition 1 = P 2 AGAM06- M
state 1 condition grade 1 Excellent 09
8.4.80 Bridge Condition br_cond_2 Percent of asset at bridge I 3 % Condition 2 = P 2 AGAM06- M
state 2 condition grade 2 Good 09
8.4.81 Bridge condition br_cond_3 Percent of asset at bridge I 3 % Condition 3 = P 2 AGAM06- M
state 3 condition grade 3 Fair 09
8.4.82 Bridge condition br_cond_4 Percent of asset at bridge I 3 % Condition 4 = P 2 AGAM06- M
state 4 condition grade 4 Poor 09
8.4.83 Bridge conditIon br_cond Overall bridge condition I 1 1, 2, 3 or 4 P 2 AGAM06- NM
state overall expressed as a whole 09
number
8.4.84 Bridge survey br_cond_dt Date that the bridge was ddmmyyyy D 8 P 1 M
date-time inspected
8.4.85 Bridge survey br_cond_in Name of the bridge inspector AN 20 P 1
operator
Kerb and Channel
8.4.86 Kerb and channel kc_cond Visually assessed condition of I 1 Code List 9.7 P 2 IPWEA
visual condition kerb and channel PN02
8.4.87 Kerb and channel kc_date Date-time that kerb and ddmmyyyy D 8 P 1
survey date-time channel survey was done
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.4.90 Pathways survey path_date Date-time that pathways ddmmyyyy D 8 P 1
date-time survey was done
8.4.91 Pathways survey path_name Name of operator that AN 20 P 1
operator pathways survey was done
by
Unsealed Roads
8.4.92 Unsealed road us_profile Condition of crossfall/cambre I 1 Code List 9.7 P 2 AGPT06-
profile to allow water to run off 09
surface
8.4.93 Unsealed us_drain Numerical rating of the I 1 Code List 9.7 P 2 AGPT06-
drainage drainage condition 09
condition
8.4.94 Gravel depth us_gv_dep Gravel depth as measured in DC 2 mm P 3 AGPT06-
OWP or as appropriate 09
8.4.95 Unsealed survey us_date Date-time that unsealed ddmmyyyy D 8 P 1
date-time survey was done
8.4.96 Unsealed survey us_name Name of operator that AN 20 P 1
operator unsealed survey was done
by
8.5 Demand
Overview
“Demand” refers to measurement of the required usage and/or traffic loading of the asset. Most road management agencies record data in some form about
the usage of the asset. Most commonly this would include traffic information. Demand asset data therefore includes data like average daily traffic, annual
traffic, percentage heavy vehicles and similar information. There are different standards and practices of measurement and recording of demand information.
Scope
The current demand on a road is most commonly measured by agencies in the form of:
• The number of vehicles using a section of road in a given period (traffic count); and/or
• The traffic loading; and/or
• The traffic composition by type.
Traffic and usage information can be represented in many ways. The Austroads Strategic Business Case includes only “current demand” however demand is
a dynamic parameter that changes over time. Historical record keeping and predictive estimates are important data requirements in terms of service
performance measurement, predictive modelling, road design and road planning.
The vehicle classification classes included in the data tables below refer to the following:
• Australian classes are as per the Austroads vehicle classification system; and
• New Zealand classes are as per the NZTA Vehicle Classification Scheme
Demand data such as traffic volume is typically referenced (spatially or linear). Accordingly an inventory level of sophistication can be applied to demand data.
In terms of applying a level of asset planning sophistication the following approach has been generally applied to each data item:
A2 Could represent AADT with some information of commercial vehicles / traffic spectrum.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
Design
8.5.1 Equivalent esa The number of equivalent standard I 9 P 2
Standard Axle axle repetitions (SAR) which would
cause the same damage as the
standard load. The standard load
is a single axle with dual wheels
carrying a total load of 80 kN
8.5.2 Is a Bus/Public bus_route Transport routes are defined and Y – Yes B 1 Y or N P 3
Transport Route attached to each road section.
Population
8.5.3 Population pop_catch Total population within the relevant I 8 # P 3
catchment (Road Authority
boundary).
Road Use
8.5.4 Vehicle vkt A measure of traffic demand and is I 10 vkt P 3
Kilometers the length of a section of road in
Travelled kilometres multiplied by the AADT
on it. The yearly VKT is the daily
VKT multiplied by the number of
days in that year (365 or 366
days).
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
8.5.5 Gross Vehicle GVM_km A measure of traffic demand and is I 10 vkt P 3
Mass kilometres the length of a section of road in
kilometres multiplied by the
cumulative Gross Vehicle Mass
(GVM) on it. The yearly GVM-km is
the daily GVM-km multiplied by the
number of days in that year (365 or
366 days).
GVM of a vehicle, means the
maximum loaded mass of the
vehicle, as follows:
a) If the Regulator has specified
the vehicle’s maximum loaded
mass under Section 57—specified
by the Regulator under that
section*; or
b) Otherwise—stated by the
vehicle’s manufacturer.
8.5.6 Equivalent ESA_km A measure of traffic demand and is I 10 vkt P 3
Standard Axles the length of a section of road in
kilometres kilometres multiplied by the
cumulative Equivalent Standard
Axles (ESA) on it. The yearly ESA-
km is the daily ESA-km multiplied
by the number of days in that year
(365 or 366 days).
ESA’s is the number of standard
axle loads that are equivalent in
damaging effect on a pavement to
a given vehicle or axle loading.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Reference
Type
PHS
Unit
8.5.7 Passenger Car PCU_km A measure of traffic demand and is I 10 vkt P 3
Unit equivalent the length of a section of road in
kilometres kilometres multiplied by the
cumulative Passenger Car Units
(PCU) on it. The yearly PCU-km is
the daily PCU-km multiplied by the
number of days in that year (365 or
366 days).
PCU is a measure involving the
conversion of different types of
vehicles into their equivalent
passenger cars in terms of
operating characteristics.
Traffic Growth
8.5.8 Annual growth (% trf_gr_all The annual growth, expressed as a DC 4 1 % P 2 NM
/ year) of all percentage growth for all vehicle
vehicle classes classes
8.6 Utilisation
Utilisation is the current usage versus current capacity and is typically presented as a ratio. The ratio defines the proportion of an asset’s available capacity
that is being used.
Most road management agencies record data in some form about the usage of the asset. Most commonly this would include traffic information. Utilisation
asset data therefore includes data like average daily traffic, annual traffic, percentage heavy vehicles, pedestrian counts, bicycle counts and similar
information. There are different standards and practices of measurement and recording of utilisation information.
Determining the capacity of the assets is typically modelled. The level of sophistication of these varies considerably. All these models will draw on inputs from
existing inventory data and intersection controls data and provide outputs such as Network Capacity (veh/hr), and Lane Capacity ([Link]).
Utilisation can be measured in two substantive ways: current utilisation; and forecast utilisation. The method used to calculate the utilisation is determined by
the road controlling authority and recorded in the appropriate data field (eg crrent utilisation, future utilisation).
Scope
The current utilisation on a road is most commonly measured by agencies in the form of:
• The number of vehicles using a section of road in a given period (traffic count); and/or
• The traffic loading; and/or
• The traffic composition by type.
• Capacity analysis is generally a modelled output.
In terms of determining capacity the required inputs will vary based on the model being used, however typically this will include inventory items such as:
Intersection types;
• 85th percentile speed
• Lane control types
• Number of lanes
• Width of lanes.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Bicycles
8.6.1 Number of cycl_hr_xx The number of bicycles in the I 5 # P 3
bicycles per hour xx- hour of the day
8.6.2 Trips per month cycl_mth The number of bicycles trips I 5 # P 3
per month
8.6.3 User cycl_user Bicyles user profiles I 250 P 3
Classification
Capacity
8.6.4 Intersection int_type Intersection control type uncontrolled, A 12 P 3
control type round about,
give way,
stop,
signalised
8.6.5 85% Speed speed_85 85% operating speed on road I 3 P 3
section
8.6.6 Turn movement turn_count Turn movement counts per I 4 P 3
counts turn type
Output
8.6.7 Model name/ util_mod Model name and version I 20 P 3
version number used to calculate
utlilisation
8.6.8 Current util_cur Ratio of current utilisation to I 2 % P 3
utilisation current capacity
8.6.9 Future utilisation util_fut Ratio of future utilisation to I 2 % P 3
current capacity or future
capacity
Pedestrians
8.6.10 Number of ped_hr The number of pedestrian in I 5 # P 3
pedestrians per the xx-th hour of the day
hour
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.6.11 Passenger km ped_km Passenger km travelled on I 5 # P 3
travelled on public transport data collected
public transport via electronic ticketing
systems
Traffic Volumes
8.6.12 Average annual aadt_all Typically the total volume of I 5 P 2 NM
daily traffic traffic (sum of vehicles
travelling in both direction on
a two-way road) at a location
over a period of 365 days
divided by 365. Practically,
the counting period should be
a minimum of 7 continuous
days and, if known, seasonal
factors would be applied.
8.6.13 Annual average aawt_all The average daily traffic I 5 P 2
weekday traffic volume at the specified
location on weekdays
(Monday to Friday). This is
expressed as number of
vehicles per day.
8.6.14 Traffic traf_cl_sy Each country has pre-defined AN 20 P 2
classification classes definition that differ
used slightly. They are based on
the number of axles, axle
spacing, weight and length of
vehicle.
New Zealand: New Zealand
specifies 14 classes
Australia: Austroads specifies
12 classes
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.6.15 Traffic traf_class Each country has pre-defined I 2 P 2
classification classes definition that differ
system class slightly. They are based on the
number number of axles, axle spacing,
weight and length of vehicle.
New Zealand: New Zealand
specifies 14 classes
Australia: Austroads specifies
12 classes
8.6.16 Number of peak_hr_v The number of vehicles at the I 6 P 2
vehicles during specified location during the
peak hour hour of the day that observes
the highest traffic volumes.
Note the period with the
highest volumes may not
commence at the start of any
hour.
8.6.17 Number of hr_vol The number of vehicles per I 6 P 2
vehicles per hour hour. xx is the xx-th hour
during the day
8.6.18 Average annual aadt_lane Typically the volume of traffic I 5 P 2
daily traffic per per lane at a location over a
lane period of 365 days divided by
365. Practically, the counting
period should be a minimum
of 7 continuous days and, if
known, seasonal factors
would be applied.
8.6.19 Annual average aawt_lane The average daily traffic I 5 P 2
weekday traffic volume per lane at the
per lane specified location on
weekdays (Monday to Friday).
8.6.20 Percentage of aadt_bke The percentage of the aadt I 3 % P 3
aadt classified as where the traffic volume is
motorbike classified as a motorbike.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.6.21 Percentage of aadt_bke_l The percentage of the aadt I 3 % P 3
aadt per lane per lane where the traffic
classified as volume is classified as a
motorbike motorbike.
8.6.22 Percentage of aadt_car The percentage of the aadt I 3 % P 2
aadt classified as where the traffic volume is
car classified as car. Light vehicle
includes cars, motorbikes and
other small vehicles
New Zealand: class 1-3
Australia: class 1-2
8.6.23 Percentage of aadt_car_l The percentage of the aadt I 3 % P 2
aadt per lane per lane where the traffic
classified as car volume is classified as car.
Light vehicle includes cars,
motorbikes and other small
vehicles
New Zealand: class 1-3
Australia: class 1-2
8.6.24 Percentage of aadt_bus The percentage of the aadt I 3 P 2
aadt classified as where the traffic volume is
bus classified as bus.
New Zealand: class 4
Australia: some vehicles
classified under classes 3, 4,
6 and 7
8.6.25 Percentage of aadt_bus_l The percentage of the aadt I 3 P 2
aadt classified as per lane where the traffic
bus per lane volume is classified as bus.
New Zealand: class 4
Australia: classes 3 and some
vehicles classified under 6-7
8.6.26 Percentage of aadt_hcv The percentage of the aadt I 3 P 2 NM
aadt classified as where the traffic volume is
heavy vehicles classified as heavy vehicles.
New Zealand: class 5-14
Australia: classes 3-12
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.6.27 Percentage of aadt_hcv_l The percentage of the aadt I 3 P 2
aadt per lane per lane where the traffic
classified as volume is classified as heavy
heavy vehicles vehicles. New Zealand: class
5-14
Australia: classes 3-12
8.6.28 Average annual aadt_cl Each country has pre-defined I 3 % Maximum P 2
daily traffic per classes definition that differ allowable
class slightly. They are based on percentage is
the number of axles, axle 100%
spacing, weight and length of
vehicle.
New Zealand: New Zealand
specifies 14 classes
Australia: Austroads specifies
12 classes
8.6.29 Average annual aadt_cl_l Each country has pre-defined I 3 % Maximum P 2
daily traffic per classes definition that differ allowable
class per lane slightly. They are based on percentage is
the number of axles, axle 100%
spacing, weight and length of
vehicle.
New Zealand: New Zealand
specifies 14 classes
Australia: Austroads specifies
12 classes
8.6.30 Number of veh_p_h_ln The number of vehicles at the I 6 P 2
vehicles during specified location during the
peak hour per hour of the day that observes
lane the highest traffic volumes per
lane. Note the period with the
highest volumes may not
commence at the start of any
hour.
8.6.31 Number of veh_hr_ln The number of vehicles of I 6 P 2
vehicles per lane traffic per hour per lane. xx is
per hour the xx-th hour during the day
8.7 Criticality
Overview
Criticality considers the importance of assets in the delivery of the organisational obligations and objectives. In a road context, this can be considered in two
ways:
• At an asset or component level, in terms of how individual the assets impact the route; and
• At a road level, in terms of the importance of that route.
The organisational objectives may include economic development, economic sustainability, safety, preservation of life, and community welfare.
Scope
The criticality of a component or route should reflect the importance of that item against the organisational obligations and objectives. These items are rated
by importance, with consideration for the potential impact to the delivery of the objectives. The scope includes:
• The assessment of components/routes to determine if their function is critical in regard to the delivery of the objectives, and
• Identification of the essential assets for prioritied management.
Precision
Purpose
Scale
Soph
Type
Industry
PHS
Unit
Ref Name Code Definition Example List Reference
8.7.1 Critical Rating crit_comp A criticality rating that I 1 Code List 9.11 P 1
describes the importance of
the item to the organisation.
8.8 Risk
Overview
Risk analysis determines the potential to gain or lose something of ‘value’, that is determining the probability of quantifiable damage, injury, liability, loss, or
any other negative occurrence caused by external or internal vulnerabilities, and that may be avoided through pre-emptive action.
Risks analysis should be undertaken on all asset related activities such as planning, design, construction, acquisition, operations and disposal. Risk
assessment is part of the process of continual improvement rather than a one-off action. Assessments need to be reviewed and updated within the risk
registers throughout an asset life.
Scope
Components of Risk
Most organisations align their risk practices with the principles contained within AS/NZS ISO 31000:2009, Risk Management – Principles and Guidelines.
Risk is quantified in terms of the consequences of an event and the associated likelihood of occurrence:
• Likelihood: defined as the chance of an event happening
• Consequence: defined as the outcome of an event, expressed qualitatively or quantitatively
Likelihood of failure is the product of an event occurring in terms of a given return period, an example matrix is summarised in the table below:
• Financial: an assets ability to deliver the desired outcomes within the financial limits.
• Environmental: an assets ability to deliver the desired outcomes within the environmental limits.
• Governance: an assets ability to deliver the desired outcomes within the reputational limits, and legislative requirements.
A typical consequence assessment is summarised in the table below. The consequence grade considers the number of people potentially affected by an
event, and whether the consequence is temporary or permanent.
Calculating Risk
To determine a risk rating score the consequence and likelihood matrix below can be used. The approach involves:
• Identifying the sources of risk that may lead to the failure of an asset
• Identifying the consequences of an event occurring and assign a consequence score for each of the consequence categories that are affected. Assign an
overall consequence score based on the highest consequence score assigned to each of the individual categories
• Predicting the likelihood of the event occurring and assign a likelihood score for each of the consequence categories that are affected. Assign an overall
likelihood score based on the highest likelihood score assigned to each of the individual categories
• Assigning a risk score based on the consequence and likelihood scores assigned.
Consequence Grade
Risk Matrix
1 2 3 4 5
Likelihood Grade
1 1 1 2 3 4
2 1 2 3 3 4
3 2 2 3 4 5
4 2 3 4 5 5
5 3 4 4 5 5
For risk management to be effectively managed for following practices need to be included as a minimum:
• Documenting risks within a risk register
• Developing mitigation and monitoring plans
• Regular review the risks to ensure the risk score is applicable
• Update the mitigation and monitoring plans as necessary.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Consequence
8.8.1 Consequence risk_co The overall consequence I 1 1 to 5 P 1 AS/NZS
Rating overall rating considering the impact ISO
of asset failure across the 31000:2009
predefined list of stakeholders
and organisational objectives
8.8.2 Consequence risk_co_hs The health and safety I 1 1 to 5 P 1 AS/NZS
Rating Health consequence rating ISO
and Safety considering the impact of 31000:2009
asset failure across the
predefined list of stakeholders
and organisational health and
safety objectives
8.8.3 Consequence risk_co_se The socio-cultural I 1 1 to 5 P 1 AS/NZS
Rating Socio consequence rating ISO
Cultural considering the impact of 31000:2009
asset failure across the
predefined list of stakeholders
and organisational
sociocultural objectives
8.8.4 Consequence risk_co_fi The financial consequence I 1 1 to 5 P 1 AS/NZS
Rating Financial rating considering the impact ISO
of asset failure across the 31000:2009
predefined list of stakeholders
and organisational financial
objectives
8.8.5 Consequence risk_co_en The environmental I 1 1 to 5 P 1 AS/NZS
Rating consequence rating ISO
Environmental considering the impact of 31000:2009
asset failure across the
predefined list of stakeholders
and organisational
environmental objectives
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.8.6 Consequence risk_co_go The governance I 1 1 to 5 P 1 AS/NZS
Rating consequence rating ISO
Governance considering the impact of 31000:2009
asset failure across the
predefined list of stakeholders
and organisational
governance objectives
General
8.8.7 Risk ID risk_id Unique identifier for risks AN 10 P 1 AS/NZS
contained within the risk ISO
register 31000:2009
8.8.8 Risk Date risk_date Date initial risk assessment ddmmyyyy D 8 dd/mm/ccyy P 1 AS/NZS
undertaken ISO
31000:2009
Likelihood
8.8.9 Likelihood Rating risk_le Overall likelihood rating I 1 1 to 5 P 1 AS/NZS ISO
Overall considering how often the 31000:2009
hazard is likely to occur
Monitoring
8.8.10 Schedule risk_mo_dt Date for next scheduled ddmmyyyy D 8 dd/mm/ccyy P 2 AS/NZS
monitoring plan review of the risk rating, ISO
review date mitigation and monitoring plan 31000:2009
8.8.11 Montioring plan risk_mo_id Unique identifier for the AN 10 P 2 AS/NZS
identifier monitoring and mitigation plan ISO
for each risk within the risk 31000:2009
register
Output
8.8.12 Risk Rating risk_rate Overall risk rating identified I 1 1 to 5 P 1 AS/NZS
Overall by likelihood and ISO
consequence 31000:2009
8.9 Resilience
Overview
Resilience of road transportation lifelines is dependent on their vulnerability to a loss of quality or serviceability, and the time taken to bring them back into
original usage state after the reduction or loss of service.
Resilience is considered in three states: Damage State, Access State, and Duration State. The reason for this is that after an event some availability may be
able to be reinstated in a relatively short time frame. These three states can be assessed for various scenarios on primary routes, and be plotted on to a GIS
layer to understand the impact of an event at a network level.
Scope
Resilience State:
Damage State:
Access State:
Duration State:
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.9.1 Event scenario resil_sc Event scenario that route/ Flood, AN 250 P 2
that route/ road road section resilience is Earthquake,
section resilience being considered for. Storm, etc
is being
considered for.
8.9.2 Damage State resil_dam Qualitive measure that I 1 1 to 5 P 2
represents the severity of
damage to the route/road
section in terms of actual or
potential damage.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.9.3 Access State resil_ava Qualitive measure that I 1 1 to 5 P 2
indicates whether the road
section would be able to be
used either at full level, at
various reduced levels or not
at all in terms of actual or
potential road section
availability.
8.9.4 Duration resil_out Indicated the duration over I 1 1 to 5 P 2
which the reoute/road section
will be in the Access State
above. Qualitive measure in
terms of the duration over
which the route/road section
will be in the Availability State
above.
Overview
Asset performance, in terms of this Standard, refers to technical levels of service (TLoS) derived from objective data and measured qualitatively.
Measurement of TLoS enables asset owners and users to understand how the network of assets is performing.
Technical performance measures currently vary significantly between road agencies and local councils. There is an option of standardisation of asset
performance standards and measures where funding bodies might require specific asset performance indicators to be provided by road agencies and local
councils as a condition of funding. These measures are typically used to aggregate information for reporting purposes and comparative analysis of
performance.
Scope
Asset performance data can be used by a wide range of stakeholders to rate the efficiency and effectiveness of how asset systems are performing. This
section incorporates a range of technically focussed asset performance measures, separated into sub-categories.
The Achievement sub-category provides a list a general data fields which will apply to performance measures within the other sub-categories.
The Asset Life sub-category provides a number of performance measures which can be applied to each of the Asset Groups listed in section 8.3 Inventory.
Performance measure targets may be aspirational, which are set without robust consideration of available budget to achieve the typically stretch target; or
performance measure targets may be achievable, which are set with due consideration of available budget. This data standard does not attempt to set targets
for performance measures; as performance measure targets are a function of available budget and risk appetite, which will vary between road management
authorities.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Achievement
8.10.1 Performance perf1_cat Performance category FINAN – A 7 Code List P 2
category Financial 9.29
8.10.2 Performance perf1_achb Required technical AN 10 P 3
measure performance value, determined
target_achievable as achievable in consideration
of available funding envelope
8.10.3 Target date for tach1_date Target date for delivery of ddmmyyyy D 8 P 3
Performance target set under Performance
measure measure target_achievable
target_achievable
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Asset Life
8.10.8 Design life life_des The total number of years the I 3 yrs P 1 M
asset is expected to provide
service, designed for a high
level of reliability (typically 90
to 95%).
Note: The Design life is
typically shorter than the
Useful life.
8.10.9 Useful life life_use_a The total number of years the I 3 yrs P 1
assessed asset is expected to provide
service, based on a subjective
assessment or engineering
estimationis, beyond which the
asset is no longer acceptable
for use.
Note: The Useful life is typically
longer than the Design life.
8.10.10 Useful life life_use_c The total number of years the I 3 yrs P 2
calculated asset is expected to provide
service, based on the
assessed/estimated mean of a
mature asset stock, beyond
which the asset is no longer
acceptable for use.
Note: The Useful life is typically
longer than the Design life.
8.10.11 Useful life life_use_m The method used to calculate DESK - I 3 yrs Code List 9.36 P 2
calculation method the useful life for the asset Desktop
8.10.12 Out of service life_e The date the asset was taken ddmmyyyy D 8 P 1
date out of service or replaced
8.10.13 End of life reason life_e_r The reason for the asset A 2 Code List P 1
being taken out of service or 9.15
replaced
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.10.14 Life achieved life_ach The number of years the I 3 yrs P 1
asset was actually in service
8.10.15 Asset age asset_age The current age of the asset I 3 yrs P 1 M
8.10.16 Remaining life life_rem_a The subjectively assessed I 3 yrs P 1 M
assessed remaining life for the asset
8.10.17 Remaining life life_rem_c The calculated remaining life I 3 yrs P 2
calculated for the asset
8.10.18 Remaining life life_rem_m The method used to calculate DESK - I 3 yrs Code List P 2
calculation the remaining life for the asset Desktop 9.36
method
Output
8.10.19 Resurfacing surf_pc The area of the total DC 3 1 % 0 to 100 P 2 M
coverage across pavement network (i.e. sealed
total network and unsealed) resurfaced (i.e.
reseal and thin asphalt on
sealed network plus granular
resheet on unsealed network),
expressed as a percentage of
the total network area at the
start of the year. Reported
annually.
8.10.20 Resheeting surf_us_pc The area of the unsealed DC 3 1 % 0 to 100 P 2 M
coverage across pavement network resurfaced
unsealed network (i.e. granular resheet),
expressed as a percentage of
the total unsealed network area
at the start of the financial year.
Reported annually.
8.10.21 Resurfacing surf_s_pc The area of the sealed DC 3 1 % 0 to 100 P 2 M
coverage across pavement network resurfaced
sealed network (i.e. reseal and thin asphalt),
expressed as a percentage of
the total sealed network area
at the start of the financial
year. Reported annually.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.10.22 Sprayed seal sseal_pc The area of the sealed DC 3 1 % 0 to 100 P 2 M
coverage across pavement network resurfaced
sealed network with a sprayed seal,
expressed as a percentage of
the total sealed network area
covered by sprayed seal at
start of the year. Reported
annually.
8.10.23 Asphalt asphalt_pc The area of the sealed DC 3 1 % 0 to 100 P 2 M
resurfacing pavement network resurfaced
coverage across with a thin asphalt treatment,
sealed network expressed as a percentage of
the total sealed network area
covered by asphalt at start of
the financial year. Reported
annually.
8.10.24 Pavement rehab_pc The area of the sealed DC 3 1 % 0 to 100 P 2 M
rehabilitation pavement network
network rehabilitated, expressed as a
coverage percentage of the total sealed
network area at the start of
the financial year. Reported
annually.
8.10.25 Major structures struct_pc The total number of major DC 3 1 % 0 to 100 P 2 M
replaced structures (i.e. bridges and
major culverts) replaced,
expressed as a percentage of
the total number of structures
across the network at start of
the financial year. Reported
annually.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.10.26 Bridges replaced bridge_pc The total number of bridges DC 3 1 % 0 to 100 P 2 M
(i.e. excluding major culverts)
replaced, expressed as a
percentage of the total
number of bridges across the
network at start of the
financial year. Reported
annually.
8.10.27 Major culverts maj_cul_pc The total number of major DC 3 1 % 0 to 100 P 2 M
replaced culverts (i.e. excluding bridges)
replaced, expressed as a
percentage of the total number
of major culverts across the
network at start of the financial
year. Reported annually.
Overview
Financial performance, in terms of this Standard, refers to Financial Level of Service (FLoS) measures that provide an indication of the financial efficiency and
effectiveness derived from objective data and measured qualitatively. Measurement of FLoS enables asset owners and users to understand how the network
of assets is performing in terms of financial return and sustainability.
Scope
Financial performance data can be used by a wide range of stakeholders to rate the financial efficiency and effectiveness of the asset system.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Development Program / Project Assessment
8.11.1 Return on rce_less1 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR less than 1.0. Performance
BCR <1 Indicators
The BCR used is that one NPI6.1.
attributed to a project when the Typically
decision to fund the project was represented as a
made. graph along with
other BCR band
widths.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.11.2 Return on rce_1to2 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR less between 1.0 and 2.0. Performance
BCR 1-2 Indicators
The BCR used is that one NPI6.1.
attributed to a project when the Typically
decision to fund the project was represented as a
made. graph along with
other BCR band
widths.
8.11.3 Return on rce_2to3 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR less between 2.0 and 3.0. Performance
BCR 2-3 Indicators
The BCR used is that one NPI6.1.
attributed to a project when the Typically
decision to fund the project was represented as a
made. graph along with
other BCR band
widths.
8.11.4 Return on rce_3to4 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR BCR less between 3.0 and 4.0. Performance
3-4 Indicators NPI6.1.
The BCR used is that one attributed Typically
to a project when the decision to represented as a
fund the project was made. graph along with
other BCR band
widths.
8.11.5 Return on rce_4to5 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR less between 4.0 and 5.0. Performance
BCR 4-5 Indicators
The BCR used is that one NPI6.1.
attributed to a project when the Typically
decision to fund the project was represented as a
made. graph along with
other BCR band
widths.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.11.6 Return on rce_great5 Percentage of total programmed DC 3 1 Graph P 3 Austroads
Construction expenditure in a financial year with National
Expenditure BCR BCR greater than 5.0. Performance
>5 Indicators NPI6.1.
The BCR used is that one attributed Typically
to a project when the decision to represented as a
fund the project was made. graph along with
other BCR band
widths.
Financial
8.11.7 Operating fin_osr The operating result (exclusive of DC 3 1 % P 2 Australian
Surplus Ratio capital income) expressed as a Infrastructure
percentage of total operating Financial
income (also exclusive of capital Management
income). It assesses the entity's Manual (AIFMM)
financial performance.
8.11.8 Net Financial fin_nflr The magnitude of net financial DC 3 1 % P 2 Australian
Liabilities Ratio liabilities relative to operating Infrastructure
income. It is calculated based on its Financial
level of debt and other financial Management
liabilities less financial assets all Manual (AIFMM)
expressed as a ratio of operating
revenue (exclusive of capital
income).
8.11.9 Asset Renewal fin_arfr The ratio of asset renewal and DC 3 1 % P 3 Australian
Funding Ratio replacement expenditure for a Infrastructure
period relative to the asset renewal Financial
and replacement expenditure Management
identified as warranted in an asset Manual (AIFMM)
management plan for the same
period. It assesses the entity's
asset renewal and replacement
performance.
NOTE: Where an entity does not
yet have a reliable forecast of
renewal requirements, it should
cautiously adopt the Asset
Sustainability Ratio as a substitute.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.11.10 Asset fin_asr The ratio of asset replacement DC 3 1 % P 2 Australian
Sustainability expenditure relative to depreciation Infrastructure
Ratio for a period. It measures whether Financial
assets are being renewed at the rate Management
they are wearing out. Manual (AIFMM)
Investment
8.11.11 Total Capital capex_tot Relatively large (material) Mo 10 2 $x P 1 Australian M
Spend expenditure, which has benefits, 103 Infrastructure
expected to last for more than 12 Financial
months. Capital expenditure Management
includes renewal, upgrade and Manual (AIFMM)
expansion expenditure.
Measured as a three-year rolling
average of historical capital spend,
including renewal, upgrade and
expansion capital expenditure.
8.11.12 Capital Spend – capex_ue Upgrade capital is expenditure which Mo 10 2 $ x 103 P 2 Australian M
Upgrade and replaces a previously existing asset Infrastructure
Expansion with enhanced capability or function, Financial
where an option existed for Management
replacement without the enhanced Manual (AIFMM)
capability or functionality (e.g.
widening the sealed area of an
existing road, replacing drainage
pipes with pipes of greater capacity).
Expansion capital is expenditure that
creates new assets to provide a new
service/output or extends the
capacity of an existing asset to new
beneficiaries (e.g. building of a new
road or building of a new culvert
where one did not previously exist).
Measured as a three-year rolling
average of historical capital spend,
excluding renewal capital
expenditure.
8.11.13 Capital Spend – capex_ren Renewal capital is expenditure on Mo 10 2 $x P 2 Australian NM
Renewals an existing asset or on replacing an 103 Infrastructure
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
existing asset, which returns the Financial
service capability of the asset up to Management
that which it had originally (e.g. Manual (AIFMM)
resurfacing or resheeting a material
section of the road network,
replacing a material section of a
drainage network with pipes of the
same capacity).
Measured as a three year rolling
average of historical capital spend,
excluding upgrade and expansion
capital expenditure.
NOTE: Histroical definitions of road
network maintenance expenditure
typically covered both maintenance
and renewal. For the avoidance of
doubt, renewal expenditure
(Capex) is not considered
maintenance expenditure (Opex).
8.11.14 Total Recurrent opex_tot Recurrent expenditure, which is Mo 10 2 $x P 1 Australian M
Spend relatively small (immaterial) or that 103 Infrastructure
which has benefits expected to last Financial
less than 12 months. Recurrent Management
expenditure is continuously Manual (AIFMM)
required to maintain and asset or
provide a service. Recurrent
expenditure includes operating and
maintenance expenditure.
Measured as a three year rolling
average of historical operating
spend, including maintenance,
operating and depreciation
expenditure.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.11.15 Recurrent opex_maint Maintenance is recurrent Mo 10 2 $x P 2 Australian NM
Spend – expenditure, which is regularly 103 Infrastructure
Maintenance required as part of the anticipated Financial
schedule of works required to Management
ensure that the asset achieves its Manual (AIFMM)
useful life and provides the
required level of service (e.g.
defect patching, guard rail
tensioning).
Measured as a three year rolling
average of historical recurrent
spend, excluding operations and
depreciation expenditure.
NOTE: Histroical definitions of road
network maintenance expenditure
typically covered both maintenance
and renewal. For the avoidance of
doubt, maintenance expenditure
(Opex) excludes renewal
expenditure (Capex).
8.11.16 Recurrent Spend opex_oper Operations is recurrent expenditure, Mo 10 2 $ x 103 P 2 Australian NM
– Operations which is continuously required to Infrastructure
provide a service (e.g. street Financial
sweeping, grass mowing, power, Management
fuel, staff, on-costs, overheads). Manual (AIFMM)
Measured as a three-year rolling
average of historical recurrent
spend, excluding maintenance and
depreciation expenditure.
8.11.17 Depreciation opex_dep Depreciation expense is the sum of Mo 10 2 $ x 103 P 2 Australian
Expense asset depreciation resulting from the Infrastructure
systematic allocation of the Financial
depreciable amount of an asset over Management
its useful life. Manual (AIFMM)
Overview
Levels of service have traditionally been presented in terms of technical or engineering focused requirements, such as intervention triggers and response time
requirements. In recognition of the increasing focus in the way the assets support the delivery of the service to the community, customer levels of service are
being used to evaluate the service performance of asset systems.
Customer levels of service (CLoS) are used by road managing agencies to monitor, evaluate and report on the service performance of the asset systems
managed by their jurisdiction to support the organisation’s stated objectives. CLoS typically measure performance in the context of road user mobility, safety,
amenity or accessibility. These outcomes are important for a range of users including car drivers, freight, emergency services, public transport operators and
for non-car based travellers such as pedestrians and cyclists.
CLoS may be measured in either a qualitative or quantitative manner. A CLoS describes the ability of the road network to provide safe and efficient access to
road users. Because CLoS are predominantly KPI focused they are often presented as metrics derived from existing datasets. Information from datasets such
as traffic volumes and speed, maintenance requests and schedules, road closures, crashes, transport asset inventories and public transport journeys are all
used to measure CLoS outcomes.
Despite efforts towards harmonising service performance measures across the roads sector, such as the Austroads National Performance Indicators, CLoS
continue to vary significantly between road agencies and local governments. A harmonised set of asset performance standards and measures may aid in
measuring performance more closely aligned to the road user’s experience. Adoption of a harmonised set of CLoS, supplemented by TLoS, will provide a
more complete set of performance measures to aid interaction of road agencies and local governments with their customers and funding agencies.
Scope
Service performance data can be used by a wide range of stakeholders to rate the efficiency and effectiveness of how asset systems are performing. This
section incorporates a range of customer focussed service performance measures, separated into sub-categories.
The Achievement sub-category provides a list a general data fields which will apply to performance measures within the other sub-categories.
Performance measure targets may be aspirational, which are set without robust consideration of available budget to achieve the typically stretch target; or
performance measure targets may be achievable, which are set with due consideration of available budget. This data standard does not attempt to set targets
for performance measures; as performance measure targets are a function of available budget and risk appetite, which will vary between road management
authorities.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Achievement
8.12.1 Performance perf_cat Performance category FINAN – Financial A 7 Code List P 2
category 9.29
8.12.2 Performance perf_ta_ac Required technical AN 10 P 3
measure performance value,
target_achievable determined as achievable in
consideration of available
funding envelope
8.12.3 Target date for perf_ta_da Target date for delivery of ddmmyyyy D 8 P 3
Performance target set under
measure Performance measure
target_achievable target_achievable
8.12.4 Performance perf_tx Required technical AN 10 P 2
measure performance value,
target_aspirational considered aspirational
without consideration of
available funding envelope
8.12.5 Target date for perf_tx_da Target date for delivery of ddmmyyyy D 8 P 2
Performance target set under Performance
measure measure target_aspirational
target_aspirational
8.12.6 Performance actual perf_act Actual service performance AN 10 P 2
value achieved.
8.12.7 Actual date for perf_a_da Actual date performance ddmmyyyy D 8 P 2
Performance actual measured for Performance
actual
Customer Experience
8.12.8 Smooth Travel ste_u_420 Proportion of travel DC 4 1 % P 3 Austroads
Exposure Urban undertaken each year on National
(4.2 IRI) urban roads with a Performance
roughness level condition of Indicators
less than 4.2 IRI NPI_4.2.1
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.9 Smooth Travel ste_r_420 Proportion of travel DC 4 1 % P 3 Austroads
Exposure Rural undertaken each year on National
(4.2 IRI) rural roads with a roughness Performance
level condition of less than Indicators
4.2 IRI NPI_4.2.2
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.15 Reported number defct_num Reported number of defects I 3 # P 2
of defects across all infrastructure
assets, reported from
Maintenance Management
System on a monthly basis.
8.12.16 Reported number defct_path Reported number of defects I 3 # P 2
of defects on across pathway assets,
pathways reported from Maintenance
Management System on a
monthly basis.
8.12.17 Reported number defct_surf Reported number of defects I 3 # P 2
of defects on across pavement assets,
pavement surface reported from Maintenance
Management System
monthly.
8.12.18 Reported number defct_rail Reported number of I 3 # P 3
of service issues defects, faults and non-
for traffic conformances to standards
restraining across traffic restraining
devices device assets (i.e. bridge
side rails, guardrails, wire
rope barriers, crash
cushions). Defects and
faults reported via
Maintenance Management
system and non-
conformances to standards
assessed via inspections.
8.12.19 Reported number defct_ligt Reported number of defects, 3 – Acceptable I 1 P 3
of service issues faults and non-conformances
for lighting to standards across lighting
assets. Defects and faults
reported via Maintenance
Management system and
non-conformances to
standards assessed via night
time inspections.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.20 Pathways meeting sci_path Percentage of pathways by I 3 % P 3
the level of service area, across the network,
standard within the defined and
documented level of service
standard.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
prior to journey. Customers
are informed at least x days
ahead of a planned event of
delays exceeding a given
threshold.
8.12.26 Proportion of wsites_len The total length of planned DC 3 1 % P 3
planned work work sites in metres,
sites expressed as a percentage
of the total network length,
measured month by month.
8.12.27 Actual travel speed work_atsu Weighted aggregate speed DC 3 1 km/hr P 3
at planned work on a representative sample
sites of planned work sites along
arterial roads and freeways
in major cities.
8.12.28 Actual delay at work_delay The delay resulting from DC 3 1 km/hr P 3
planned work planned works. Weighted
sites aggregate speed on a
representative sample of
planned work sites minus
the Nominal Travel Speed.
Public Transport
8.12.29 Public transport pt_reliab Public transport reliability I 3 % P 3
reliability
8.12.30 Public transport ttime_rel Public transport travel time. I 3 % P 3
travel time reliability % of time target is met
Road Safety
8.12.31 Crash date crash_date Crash date ddmmyyyy D 8 dd/mm/ccyy P 2 AS/NZS ISO
31000:2009
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Austroads
National
Performance
(Road Safety)
Indicators
8.12.33 Road user crash_r_us Vehicles/road users A 3 Code List P 2 Base data
involved involved in crash. 9.9 fields used
Identify the vehicle types to capture
involved in all reported core input
crashes including cyclists data for
and pedestrians Austroads
National
Used to facilitiate reporting Performance
for a number of Road (Road
Safety measures that rely Safety)
on data relating to reported Indicators
crashes
8.12.34 Crash severity crash_sev Crash severity, categorised A 1 Code List P 2 Base data
as one of fatal, serious, 9.10 fields used to
minor, non-injury. capture core
input data for
Used to facilitiate reporting Austroads
for a number of Road Safety National
measures that rely on data Performance
relating to reported crashes (Road Safety)
Indicators
8.12.35 Crash count crash_cnt Total average annual crash I 4 # P 2 Base data
count, by location. fields used
to capture
core input
data for
Austroads
National
Performance
(Road
Safety)
Indicators
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.36 Crash count crash_yrs Number of years over which I 2 yrs P 2 Base data
number of years the average annual crash fields used
of data count was calculated. to capture
core input
data for
Austroads
National
Performance
(Road
Safety)
Indicators
8.12.37 Total crash count crash _p Total crashes per 100,000 I 4 #/ P 3
(Population) population km*108
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.41 Serious Casualty scc_t Serious Casualty Crashes DC 3 1 #/ P 3 Austroads
Crashes (Vehicle- per 100 million veh-kms km*108 National
Kilometres Performance
Travelled) Indicators
NPI2.2
8.12.42 Number of Road sf Count of fatalities resulting I 4 # P 2 Input field
Fatalities from road crashes during for
the year Austroads
National
Performance
Indicators
NPI2.3 and
NPI2.4
8.12.43 Road Fatalities sf_p Fatalities per 100,000 DC 3 1 #/ P 3 Austroads
(Population) population p*105 National
Performance
Indicators
NPI2.3
8.12.44 Road Fatalities sf_t Fatalities per 100 million DC 3 2 #/ P 3 Austroads
(Vehicle- veh-kms km*108 National
Kilometres Performance
Travelled) Indicators
NPI2.4
8.12.45 Number of sph Count of persons admitted I 6 # P 2 Input field
Persons to hospital resulting from for
Hospitalised road crashes per year. Austroads
National
Performance
Indicators
NPI2.5 and
NPI2.6
8.12.46 Persons sph_p Persons hospitalised per DC 4 1 #/ P 3 Austroads
Hospitalised 100,000 population p*105 National
(Population) Performance
Indicators
NPI2.5
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.47 Persons sph_t Persons hospitalised per DC 3 1 #/ P 3 Austroads
Hospitalised 100 million veh-kms km*108 National
(Vehicle- Performance
Kilometres Indicators
Travelled) NPI2.6
8.12.48 Social Cost of ssc Average social cost per Mo 10 2 $ P 2 Input field
Serious Casualty serious casualty crash. for
Crash Austroads
National
Performance
Indicators
NPI2.7 and
NPI2.8
8.12.49 Social Cost of ssc_p AU$ million cost of serious Mo 10 2 $/ P 3 Austroads
Serious Casualty casualty crashes per 100,000 p*105 National
Crashes population Performance
(Population) Indicators
NPI2.7
8.12.50 Social Cost of ssc_t $ million cost of serious Mo 10 2 $/ P 3 Austroads
Serious Casualty casualty crashes per 100 km*108 National
Crashes (Vehicle- million veh-kms Performance
Kilometres Indicators
Travelled) NPI2.8
8.12.51 Collective Road saferisk_c Average annual fatal and A 4 Code List P 3 kiwiRAP
Safety Risk serious injury crashes per 9.44
km
Collective Road Safety Risk
is a measure of the total
number of fatal and serious
injury crashes per kilometre
over a section of road.
(Collective Road Safety
Risk can also be described
as the Crash Density)
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.52 Personal Road saferisk_p Average annual fatal and A 4 Code List P 3 kiwiRAP
Safety Risk serious injury crashes per 9.44
100 million vehicle-km
Personal Road Safety Risk
is a measure of the danger
to each individual using the
state highway being
assessed. (Personal Road
Safety Risk can also be
described as the Crash
Rate)
Travel Speed
8.12.53 Nominal Travel ntt Nominal travel time of link, I 3 min P 3 Input field for
Time measured in minutes. Austroads
National
Performance
Indicators
NPI7.2,
NPI7.3.1,
NPI7.3.2,
NPI7.3.3. and
NPI7.3.4
8.12.54 Actual Travel att Actual travel time of link, I 3 min P 3 Input field
Time measured in minutes. for
Austroads
National
Performance
Indicators
NPI7.3.1,
NPI7.3.2,
NPI7.3.3.
and
NPI7.3.4
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.55 Mean Travel Time mtt Mean travel time of link, I 3 min P 3 Input field
measured in minutes. for
Austroads
National
Performance
Indicators
NPI7.1.1,
NPI7.1.2,
NPI7.1.3,
NPI7.1.4,
NPI7.4.1,
NPI7.4.2,
NPI7.4.3
and
NPI7.4.4.
8.12.56 Standard Deviation sdtt Standard Deviation of travel DC 3 2 P 3 Input field for
of Travel Times times of link. Austroads
National
Performance
Indicators
NPI7.4.1,
NPI7.4.2,
NPI7.4.3 and
NPI7.4.4.
8.12.57 AM Peak Actual atsu_amp Weighted aggregate speed DC 3 1 km/hr P 3 Austroads
Travel Speed (measured over the full National
(Urban) financial year) on a Performance
representative sample of Indicators
arterial roads and freeways NPI 7.1.1
in major cities during AM
peak hours.
8.12.58 PM Peak Actual atsu_pmp Weighted aggregate speed DC 3 1 km/hr P 3 Austroads
Travel Speed (measured over the full National
(Urban) financial year) on a Performance
representative sample of Indicators
arterial roads and freeways NPI 7.1.2
in major cities during PM
peak hours.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.59 Off Peak Actual atsu_off Weighted aggregate speed DC 3 1 km/hr P 3 Austroads
Travel Speed (measured over the full National
(Urban) financial year) on a Performance
representative sample of Indicators
arterial roads and freeways NPI 7.1.3
in major cities during off
peak hours.
8.12.60 All Day Actual atsu_day Weighted aggregate speed DC 3 1 km/hr P 3 Austroads
Travel Speed (measured over the full National
(Urban) financial year) on a Performance
representative sample of Indicators
arterial roads and freeways NPI 7.1.4
in major cities over the
whole day.
8.12.61 Nominal Travel ntsu Weighted aggregate speed DC 3 1 km/hr P 3 Austroads
Speed (Urban) (measured over the full National
financial year) on a Performance
representative sample of Indicators NPI
arterial roads and freeways 7.2
in major cities, assuming
vehicles travel at the posted
speed limit.
8.12.62 AM Peak cgi_amp Difference between Actual DC 3 1 Min/km P 3 Austroads
Congestion and Nominal Travel Time National
Indicator (Urban) (measured over the full Performance
financial year) — delay from Indicators
traffic conditions which do NPI 7.3.1
not permit travel at the
posted speed limit during
AM Peak hours.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.63 PM Peak cgi_pmp Difference between Actual DC 3 1 Min/km P 3 Austroads
Congestion and Nominal Travel Time National
Indicator (Urban) (measured over the full Performance
financial year) — delay from Indicators
traffic conditions which do NPI 7.3.2
not permit travel at the
posted speed limit during
PM Peak hours.
8.12.64 Off Peak cgi_off Difference between Actual DC 3 1 Min/km P 3 Austroads
Congestion and Nominal Travel Time National
Indicator (Urban) (measured over the full Performance
financial year) — delay from Indicators
traffic conditions which do NPI 7.3.3
not permit travel at the
posted speed limit during off
peak hours.
8.12.65 All Day Congestion cgi_day Difference between Actual DC 3 1 Min/km P 3 Austroads
Indicator (Urban) and Nominal Travel Time National
(measured over the full Performance
financial year) — delay from Indicators NPI
traffic conditions which do 7.3.4
not permit travel at the
posted speed limit over the
whole day.
8.12.66 AM Peak vtt_amp Variability of travel time DC 3 1 % P 3 Austroads
Variability of (measured over the full National
Travel Time financial year) on a Performance
(Urban) representative sample of Indicators
arterial roads and freeways NPI 7.4.1
in the urban metropolitan
area during AM Peak hours.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.12.67 PM Peak vtt_pmp Variability of travel time DC 3 1 % P 3 Austroads
Variability of (measured over the full National
Travel Time financial year) on a Performance
(Urban) representative sample of Indicators
arterial roads and freeways NPI 7.4.2
in the urban metropolitan
area during PM Peak hours.
8.12.68 Off Peak vtt_off Variability of travel time DC 3 1 % P 3 Austroads
Variability of (measured over the full National
Travel Time financial year) on a Performance
(Urban) representative sample of Indicators
arterial roads and freeways NPI 7.4.3
in the urban metropolitan
area during off peak hours.
8.12.69 All Day Variability vtt_day Variability of travel time DC 3 1 % P 3 Austroads
of Travel Time (measured over the full National
(Urban) financial year) on a Performance
representative sample of Indicators
arterial roads and freeways NPI 7.4.4
in the urban metropolitan
area over the whole day.
Unplanned Incidents
8.12.70 Time to respond to inc_r_time Incident response time. Time 30/06/[Link] DT 14 P 2
incident to respond and restore
service from the time of
event occurring/reported
User Satisfaction
8.12.71 User Satisfaction usi The USI is an indicator 5 - Very I 1 Code List P 3
Index which measures road users’ Dissatisfied 9.72
satisfaction with the road
system. Index of users'
qualitative evaluation of
satisfaction with road
system outcomes
expressed as a mean score
out of 5.
8.13 Access
Overview
Access and restrictions for the transport network/system includes the factors that affect or limit travel use or behaviour by some or all users of the road asset,
often based on some characteristic of the user.
Access and restrictions can be permanent or temporary. Those that are permanent, once installed take significant process to change and thus rarely change.
To manage the restriction or empowerment significant warning needs to be located within the road corridor and consistent supporting systems like signage in
place.
Scope
Permanent access and restrictions or mode empowerment are usually focused on strategic network level outcomes and are quite specific. To ensure those
vehicles to be excluded or empowered are addressed usually there will be detailed legal background to the situation.
Temporary access control can be used as an operational management tool through applying periodic, seasonal, or temporary to address specific local
conditions. Periodic control is most often associated with facilities like schools and typically major sports stadia, when there are specific times that controls are
required to manage operational safety and efficiency.
Access and restrictions are recorded using differing transport datasets for permanent or temporary situations. The need for on-road warning and legal
requirements for permanent controls means they are embedded into the network assets through warning signage and road markings. Mapping of permanent
restrictions is helpful to understand the strategic nature of them, this also suits enforcement since some controls can cover large areas and many links within a
network.
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Identification
8.13.1 Restriction ID restr_id Unique identification code AN 10 D 1
for the restriction
8.13.2 Restriction restr_type The restriction type. DIR – Direction A 10 Code List 9.39 D 1 M
type
8.13.3 Restriction restr_cse The reason for the Weather A 10 Code List 9.38 D 1 M
reason restriction being applied
8.13.4 User group restr_app The user group that the MOTORB – Motor A 6 Code List 9.40 D 1 M
restriction restriction applies to. bikes
applies to
8.13.5 Restriction restr_unit Unit for the value A 2 m – metres D 1 M
unit dimensioning the kg – kilograms
restriction.
8.13.6 Restriction restr_val Unit of measure for the 10.28 metres DC 8 2 D 1
value restriction
8.13.7 Organisation restr_resp The organisation A – asset owned by A 1 A – asset owned by D 1
responsible responsible for the asset agency agency
causing the restriction O – asset owned by
others
8.13.8 Restriction restr_ownr The owner of the asset A 1 D 1
owner causing the restriction
Time Period
8.13.9 Restriction restr_stat The status of the P - permanent A 1 P - permanent D 1
status restriction. T - temporary
8.13.1 Restriction restr_peri The time period the C - continuous A 1 C - continuous (24/7) D 1
0 period restriction applies (24/7) P - periodic
8.13.1 Restriction restr_s The date the restriction 38533 D 8 D 1
1 start date starts
8.13.1 Restriction restr_e The date the restriction 38533 D 8 D 1
2 end date ends
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.13.1 Restriction restr_day The days that the A 20 M,T,W,TH,F,SA,SU D 1
3 day restriction applies.
8.13.1 Restriction restr_t_s The time the restriction 30/06/[Link] DT 14 D 1
4 start time starts 4
8.13.1 Restriction restr_t_e The time the restriction 30/06/[Link] DT 14 dd/mm/ccyy:hh:mm:ss D 1
5 end time ends 0
Overview
The purpose of this function group is to provide a data set for planning, describing and capturing maintenance and forward works and the associated costs.
This data is currently used by road agencies for a variety of purposes including:
Traffic Advisory Active physical road works activities are communicated to road users, typically via a publically accessed website or digital
notification subscription service, by the road agencies. This information promotes road network efficiency;
Asset Register Physical works achievement, principally capital and renewal works, should be reflected in the asset register and any related
financial registers. The capture of this information provides a trigger for action and the basis for reconciling any updates;
Valuation Impacts Capital and renewal projects directly impact the asset valuation through the provision of new assets. This data set will provide
the basis for recognising new assets and the associated capital cost. The costs alone could also provide the basis for
establishing appropriate replacement costs across the asset portfolio;
Investment Profiles The capture of construction, renewal and maintenance costs over time will provide the basis for producing historic investment
profiles for each asset group. This information may also provide the basis for projecting future costs profiles;
Intervention Parameters Defining the intervention triggers which may prompt road agencies to undertake works on the basis of safety, condition, cost
of maintenance, efficiency (due to the proximity of similar or complementary works) or the consequences of asset failure. The
treatment type will depend of the trigger parameter;
Intervention Criteria Determining the point at which intervention is warranted in terms of level of service condition or least cost where accumulated
historic and future maintenance costs exceed the cost of the treatment proposed;
Replacement Analytics The recording of the expected useful life at the time of construction will provide the basis for determining the actual return on
capital investment. Calculating the remaining life will assist to determine the anticipated end of asset life and renewal or
replacement timing and cost;
Cost Estimates Recording works achievement with the related cost will provide a basis for refining future cost estimates for similar works;
Condition Indicator Rising maintenance costs, associated with the same asset, can be an empirical indicator of asset condition and potential
remaining life; and
Treatment Selection Cost monitoring and related condition analysis will provide an indication of systemic maintenance issues where accumulated
cost can be compared to more extensive treatments beyond continued maintenance. Treatment selection analysis requires a
sound understanding of accumulated costs as well as a predicted future works and costs.
Scope
The capture of works and costing data can impact on management and investment decisions from a number of sources for the delivery of:
• Capital Projects inclusive of asset upgrades;
• Rehabilitation, Routine and Planned Maintenance; and
• “Special” Road Projects.
Works and Costing data is a critical indicator in investment decisions and can be accessed from a number of sources including:
• Industry established tools including pavement management systems (estimated costs), maintenance management systems (achieved costs and works);
• Industry publications (estimated costs); and
• Financial management systems (capital costs etc.).
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Forward Works Plan
8.14.1 Forward works fwp_treat The proposed FWP treatment Replace A 5 Code List P 2 M
program category 9.21
8.14.2 Forward works fwp_reason The reason for the treatment High maintenance costs A 10 Code List P 2 M
program 9.20
treatment reason
8.14.3 Planned forward fwp_yr_s This is the first year of the yyyy D 4 yrs P 2 M
work treatment financial year.
start year For example: 2016 for the
2016_2017 financial year
8.14.4 Forward works fwp_start This is the start of the I 6 m L 2 M
program forward works program
treatment treatment length
location start
8.14.5 Forward works fwp_end This is the end of the forward I 6 m L 2 M
program works program treatment
treatment length
location end
8.14.6 Forward work fwp_param The reason for planning a Safety, condition, asset A 20 L 2
program treatment preservation, end of
intervention economic life
parameter
8.14.7 Forward work fwp_thresh Defining the parameter or Texture < 0.6mm AN 20 L 2 M
program condition that triggers the (safety)
intervention intervention treatment
threshold
8.14.8 Forward works fwp_cest This is the estimated cost MO 10 2 $ P 2 M
treatment allocated to the future
estimated cost treatment
8.14.9 Planned forward fwp_end_yr This is the planned year that I 4 Yrs P 2 M
treatment end the treatment in the work
year program ends
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
Maintenance
8.14.10 Maintenance mt_def_id Unique identification number AN 10 P 2
defect ID that relates to the defect
8.14.11 Defect mt_def A description of the identified Pot holes A 20 Code List P 2 M
description hazard or defect 9.12
8.14.12 Status of work mt_status The status of the work Programmed A 2 Code List P 2 M
identified to address the 9.73
recorded defect
8.14.13 Unit for mt_unit The unit for payment for the sqm - Square metres A 3 Code List P 2
payment work activity used to remedy 9.71
the defect
8.14.14 Work quantity mt_quan The quantity of the actual DC 7 1 P 2 M
work completed to address
the recorded defect, for a
given activity
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.14.19 Defect liability mt_dlp_e End date of defects liability ddmmyyyy D 8 P 3
end date period
8.14.20 Source mt_id The hazard or defect is Routine inspection or AN 20 P 3
Identification identified from a routine External Source
patrol inspection activity or
from an external source (call
centre).
8.14.21 Source mt_ref Enquiry Tracking System 500759144 AN 20 P 3
Identification reference number or similar
Reference
8.14.22 Date and time mt_date_cr The date and time that the dd/mm/ccyy:HH:MM:SS DT 14 P 3
of creation hazard or defect was
identified or of notification
from an external source
8.14.23 Intervention mt_int_par The reason for undertaking Safety, condition, asset A 20 P 3
parameter or planning the repair of a preservation
hazard or defect.
8.14.24 Intervention mt_int_thr The point at which Potholes greater than AN 20 P 3
threshold intervention is required. 300mm diameter and
greater than 100mm
deep, all other potholes
Precision
Purpose
Industry
Ref Name Code Definition Example List
Scale
Soph
Type
Reference
PHS
Unit
8.14.28 Activity group mt_act_grp The overall work activity group Reactive Mainatenance A 12 Code List 2 M
9.25
8.14.29 Work activity mt_act The work activity that is Repaint, remove A 20 Code List P 2 M
planned or has been 9.25
undertaken
8.14.30 Maintenance mt_cyc The timing of the cycle which Monthly, yearly, summer, A 20 1
cycle the work activity is undertaken winter
Output
8.14.31 Forward work fwp_cost_a This is for completed works Mo 10 2 $ P 2
treatment actual and is an all inclusive cost to
completed cost do the work
8.14.36 Actual work treat_s_a This is the date that the actual ddmmyyyy D 8 P 1
treatment start treatment in the work program
date started
8.14.37 Actual work treat_e_a This is the date that the actual ddmmyyyy D 8 P 1
treatment end treatment in the work program
date ended
Code Description
Table 9.1: Above-Below Retain Wall
POLES Poles
Code Description PUBLIC ART Public Art
BANK Bank PUBLIC TOILET Public Toilets
C-PROP Council property RETAINING Retaining Walls
WALL
DWY Driveway
ROAD Road Barriers
OPEN Open Space BARRIER
PATH Path SHELTER Shelters
PRIV Private Property SIGN Signs
ROAD Roadway SLOPE Slopes
SEA Sea STRUCTURE Structures
STRU Structure TABLE DRAIN Table Drains
WCOURSE Waterway TACTILE Tactile Paving
PAVING
TRAFFIC Traffic management Devices
Table 9.2: Asset Class DEVICE
TRAFFIC Traffic Signals
Code Description
SIGNAL
AMENITY Amenities TREE Trees
BINS Bins TUNNEL Tunnels
BRIDGE Bridge / Major Culvert VEHICLE Vehicle Crossings
MAJOR CROSSING
CULVERT
CULVERT Culverts (Minor)
MINOR Table 9.3: Asset Status
FENCE Fences
Code Description
ITS ITS Assets
ABN Abandoned or Disused
KERB AND Kerb and Channel
CHANNEL INACTIVE Not in current use, however
available
LANDSCAPING Landscaping
INUSE In-Use
LIGHTING Lighting
OTHER Other Use
LINEMARKING Linemarking Assets
PLANNED Planned
MECH AND Mechanical and Electrical Assets
ELEC REM Removed
PATHWAY Pathways
PAVEMENT Pavement
PAVEMENT Pavement Surfacing
SURFACING
PIT Pits
LITTER Litter
LOOSE Loose
LOW SURF Low Surface
Table 9.17: Fence Function Table 9.21: Forward Works Program Reason
FIRE-SPLN Fire Protection - Sprinkler Lines VAC-PTR Ventilation & Air conditioning -
Pressure transducer
FIRE-SPR Fire Protection - Sprinkler heads
VAC-SAT Ventilation & Air conditioning -
FIRE-STR Fire Protection - Strainer Sound attenuator
FIRE-TMS Fire Protection - Temperature VAC-SNS Ventilation & Air conditioning -
sensor Sensor
Code Description
Table 9.32: Pipe Type
GPT Gross Pollutant Trap
Code Description LTSK Litter Sock
CLEAN A pipe that carries clean roof OWSP Oil & Water Separator
water
SDTR Sediment Trap
CULVERT Minor culvert
SNTR Sand Trap
INLET Inlet
TRRT Trash Rack/Rubbish Trap
OPEN Open drain
OUTFALL Outfall discharge point
Table 9.36: Power Source
OVERFLOW Pipe that carries excess water to
or from a pit Code Description
PIPE A pipe used to convey liquids BATTERY Battery Supply
SUBSOIL A slotted or perforated pipe laid GENERATOR Power Generator (Petrol or
below ground Diesel)
GRID Direct off the power grid
Table 9.33: Pit Construction Type MAIN Mains power supply
SOLAR Solar Panels
Code Description
WIND Wind Turbine
AN Annealed
CAST Cast-insitu
Table 9.37: Remaining Asset Life Calculation
CORR Corrugated
Method
EX Extruded
Code Description
F Folded
DESK Desktop assessment
GC Gravity cast
ENG Engineering model
HD Hard drawn
FIELD Field Assessment
LB Lock bar
MC Mandrill cast
PC Precast
Table 9.38: Restriction Reason Table 9.41: Retain Wall Restraint Type
Code Description
Table 9.40: Restriction User Group GUARD Guardrail
Code Description NJB New Jersey Barrier
ALL All vehicles NOISE Noise Attenuation
ALLXB All vehicles except buses SAFETY Safety barrier
BUS Buses SIGHT Sight rail
CAR Cars WIRE Wire rope
CYCL Cyclists
HCV Heavy Commercial vehicles Table 9.44: Safety Related Risk Rating
MOTORB Motorbikes
Code Description
PED Pedestrians
LOW Collective Risk ≤0.039
Personal Risk ≤4
LOWMED Collective Risk 0.04 ≤ 0.069
Personal Risk 4 ≤ 4.9
MED Collective Risk 0.07 ≤ 0.10
Personal Risk 5 ≤ 6.9
MEDHIGH Collective Risk 0.11 ≤ 0.189
Personal Risk 7 ≤ 8.9
HIGH Collective Risk 0.19+
Personal Risk 9+
Code Description
BUS Bus Table 9.52: Slope Material
Code Description
Table 9.69: Tunnel Structure Type DRC Depreciated Replacement Cost
Code Description ODRC Optimised Depreciated
Replacement Cost
ARCH Arch
RC Replacement Cost
OVER Overpass
UND Underpass
Table 9.74: Work Status
Code Description
cu Cubic Metres
Ea each
hr Hours
kg Kilograms
km Kilometres
l Litres
m Metres
sqm Square metres
t Tonnes
Asset is something that has potential or actual value to an organisation. Value can be tangible or intangible,
financial or non-financial. Tangible assets are physical assets which refer to equipment, inventory and
properties owned by the organisation. Tangible assets are the opposite of intangible assets, which are non-
physical assets such as leases, brands, digital assets, use rights, licences, intellectual property rights,
reputation or agreements.
Asset function is used to represent one or more asset groups that perform the same function within an
asset group.
Asset group assets having common characteristics that distinguish them separately (different manufacturer,
different specification or different components) within an asset function.
Asset information is the combined set of data (graphical and non-graphical) and documents (drawings,
manuals, plans, certificates) required to support the management of assets over the assets life cycle.
Asset information management is the discipline of managing the asset-related data and documents to a
sufficient quality to support organisational objectives and outcomes.
Asset information repository a recognised physical or electronic location for the storage and management
of asset information.
Asset information repository custodian a person responsible for managing an asset information
repository and the processes related to the creation and maintenance of the information and provision of
access to the information in the repository.
Asset information system a set of interrelated repositories of structured asset information and related
processes required to manage the asset portfolio over the life cycle.
Asset portfolio assets that are within the scope of the asset management system.
Asset register contains the definition and description of each asset in the asset portfolio. The asset register
includes all the data required to ensure unique identification of the asset.
Availability the measure of the percentage of time that an item or system is available to perform its
designated function.
Corridor is a linear zonal area within a boundary and defined by a start and end node that contains road
infrastructure assets to support the operation of transport services.
Data information collected and stored but not yet interpreted or analysed (graphical and non-graphical).
Data harmonisation is to combine data definition and format from heterogeneous sources into integrated,
consistent and unambiguous data specification to create unified understanding and to facilitate data sharing
between organisations.
Defect an irregularity or fault in the asset that requires attention. Actions may include cleaning, repair, or
further inspections.
Document information for use in the briefing, design, construction, operation, maintenance and disposal of a
project or asset, including but not limited to correspondence, drawings, schedules, specifications,
calculations, spreadsheets, reports, manuals and certificates.
Dynamic data collected over time about how the asset is operating, performing, its condition, work done and
measurements which change through its operation and maintenance.
Guessed is a term used to describe the accuracy of the data being recorded; It indicates best judgement of
the person providing the data, without any basis of measure.
Life cycle stages for an asset from conception through to disposal and any residual risks or liability period.
Maintainability is a characteristic of design and installation, expressed as the probability that an item will be
restored to operating condition, within a given period, using prescribed procedures and resources.
Measured is a term used to describe the accuracy of the data being recorded; It indicates that the data is
based upon a recognised standard and system of measure.
Metadata is data that provides information about other data. Two types of metadata exist: structural
metadata and descriptive metadata. Structural metadata is data about the containers of data. Descriptive
metadata uses individual instances of application data or the data content.
Reliability the probability that a specified item will perform a specified function within a defined environment,
for a specified length of time
Rural Classification where the posted road speed limit is greater than 70 km/hr.
Static data (or configuration data) defines the assets themselves (their design data) and the normal
conditions in which they operate and interact with other assets.
Urban Classification where the posted road speed limit is 70 km/hr or less.
References
Austroads (2007) AGAM05B-07. Guide to Asset Management Part 5B: Roughness. Sydney, Austroads.
Austroads (2007) AGAM05C-07. Guide to Asset Management Part 5C: Rutting. Sydney, Austroads.
Austroads (2008) AGAM05D-08. Guide to Asset Management Part 5D: Strength. Sydney, Austroads.
Austroads (2006) AGAM05E-06. Guide to Asset Management Part 5B: Cracking. Sydney, Austroads.
Austroads (2009) AGAM05F-09. Guide to Asset Management Part 5B: Skid Resistance. Sydney, Austroads.
Austroads (2009) AGAM05G-09. Guide to Asset Management Part 5G: Texture. Sydney, Austroads.
Austroads (2011) AGPT05-11. Guide to Pavement Technology Part 5: Pavement Evaluation and Treatment
Design. Sydney, Austroads.
Austroads (2009) AGAM05A-09. Guide to Asset Management Part 5A: Inventory. Sydney, Austroads.
Austroads (2005) AP-R276/05. Consistency in Approaches to Road Network Segmentation and Data
Aggregation – Review of Current Practice. Sydney, Austroads.
Austroads (2006) AP-R289/06. Guidelines for the Development of a Level of Service Framework Based on
Community Consultations. Sydney, Austroads.
Austroads (2014) AGPT04B-14. Guide to Pavement Technology Part 4B: Asphalt. Sydney, Austroads.
Austroads (2015) AP-C87-15. Austroads Glossary of Terms (2015 Edition). Sydney, Austroads.
Bureau of Infrastructure, Transport and Regional Economics (2015). Australian Infrastructure Statistics –
Yearbook 2015. Canberra, Department of Infrastructure and Regional Development.
Australian Local Government Association (2015). National State of the Assets Report 2015. ACT, ALGA.
WALGA (2013/14). Report on Local Government Road Assets and Expenditure 2013/14. WALGA.
Western European Road Directors, Sub-Group Road data (2003). Data Management for Road
Administrations A Best Practice Guide, Version 2.0. Western European Road Directors
Austroads (2009) AGAM05H-09. Guide to Asset Management Part 5H: Performance Modelling. Sydney,
Austroads.
Austroads (2009) AGAM06-09. Guide to Asset Management Part 6: Bridge Performance. Sydney,
Austroads.
Austroads (2009) AGAM07-09. Guide to Asset Management Part 7: Road Related Assets Performance.
Sydney, Austroads.
Institute of Public Works Engineering Australasia (2015). International Infrastructure Management Manual
(IIMM), 5th Edition. IPWEA
The Road Efficiency Group (2014). One Network Road Classification Performance Measures, Final. The
Road Efficiency Group.
Institute of Public Works Engineering Australasia (2015). Australian Infrastructure Financial Management
Manual (AIFMM), Australian Edition 2015. Sydney, IPWEA
ISO (2014) ISO 55001:2014(E). Asset management – Management systems: Requirements, First Edition.
Switzerland, ISO
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Network Road Length Km road_len sum of [road_len]
Dimensions
Lane Kilometre Km lanekm_len sum of [lanekm_len]
Sealed Road Km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
psurf_stat
Unsealed Road Km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
psurf_stat
Sealed Urban Km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Road psurf_stat and where [traf_set] = “U”
traf_set
Sealed Rural Km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Road psurf_stat and where [traf_set] = “R”
traf_set
Unsealed Urban Km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Road psurf_stat and where [traf_set] = “U”
traf_set
Unsealed Rural Km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Road psurf_stat and where [traf_set] = “R”
traf_set
Bridges Number Num asset_id Count of [asset_id) where [asset_clas] =
asset_clas “bridge major culvert”
Or
no_str_bri
no_str_cul [no_str_bri] + [no_str_cul]
Length m br_len Sum of [br_len]
Length Timber m br_len Sum of [br_len] where [br_dek_mat] =
br_dek_mat “timber”
Tunnels Number Num asset_id Count of [asset_id] where [asset_clas] =
asset_clas “tunnel”
Length m tun_len Sum of [tun_len]
Length Lined and m tun_len Sum of [tun_len] where [tun_serv] = “S”
Serviced tun_serv
Valuation Replacement $ value Sum of [value] where [value_type] =
Cost value_type “replacement cost” and where [asset_clas] =
asset_clas “pavement + pavement surfacing + bridge
major culvert + tunnel”
Network Traffic Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
Use and Volume ALL National link_s_len where [ctype_onrc] = “NAT” or “NHV”
Demand Classification ctype_onrc
Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
ALL Regional link_s_len where [ctype_onrc] = “REG”
Classification ctype_onrc
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Network Traffic Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
Use and Volume ALL Arterial link_s_len where [ctype_onrc] = “ART”
Demand (continued) Classification ctype_onrc
(continued)
Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
ALL Primary link_s_len where [ctype_onrc] = “PC”
Collector ctype_onrc
Classification
Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
ALL Secondary link_s_len where [ctype_onrc] = “SC”
Collector ctype_onrc
Classification
Average AADT Num aadt_all Weighted average [aadt_all] by [link_s_len]
ALL Access link_s_len where [ctype_onrc] = “ACC” or “ALV”
Classification ctype_onrc
Percent- Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
age HCV HCV National link_s_len where [ctype_onrc] = “NAT” or “NHV”
Classification ctype_onrc
Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
HCV Regional link_s_len where [ctype_onrc] = “REG”
Classification ctype_onrc
Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
HCV Arterial link_s_len where [ctype_onrc] = “ART”
Classification ctype_onrc
Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
HCV Primary link_s_len where [ctype_onrc] = “PC”
Collector ctype_onrc
Classification
Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
HCV Secondary link_s_len where [ctype_onrc] = “SC”
Collector ctype_onrc
Classification
Average AADT Num aadt_hcv Weighted average [aadt_ hcv] by [link_s_len]
HCV Access link_s_len where [ctype_onrc] = “ACC” or “ALV”
Classification ctype_onrc
Traffic Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
Growth %Growth ALL link_s_len where [ctype_onrc] = “NAT” or “NHV”
National ctype_onrc
Classification
Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
%Growth ALL link_s_len where [ctype_onrc] = “REG”
Regional ctype_onrc
Classification
Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
%Growth ALL link_s_len where [ctype_onrc] = “ART”
Arterial ctype_onrc
Classification
Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
%Growth ALL link_s_len where [ctype_onrc] = “PC”
Primary Collector ctype_onrc
Classification
Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
%Growth ALL link_s_len where [ctype_onrc] = “SC”
Secondary ctype_onrc
Collector
Classification
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Network Traffic Average % trf_gr_all Weighted average [trf_gr_all] by [link_s_len]
Use and Growth %Growth ALL link_s_len where [ctype_onrc] = “ACC” or “ALV”
Demand (continued) Access ctype_onrc
(continued) Classification
HCV Average % trf_gr_hcv Weighted average [trf_gr_hcv] by [link_s_len]
Growth %Growth HCV link_s_len where [ctype_onrc] = “NAT” or “NHV”
National ctype_onrc
Classification
Average % trf_gr_hcv Weighted average [trf_gr_ hcv] by
%Growth HCV link_s_len [link_s_len] where [ctype_onrc] = “REG”
Regional ctype_onrc
Classification
Average % trf_gr_hcv Weighted average [trf_gr_ hcv] by
%Growth HCV link_s_len [link_s_len] where [ctype_onrc] = “ART”
Arterial ctype_onrc
Classification
Average % trf_gr_hcv Weighted average [trf_gr_ hcv] by
%Growth HCV link_s_len [link_s_len] where [ctype_onrc] = “PC”
Primary Collector ctype_onrc
Classification
Average % trf_gr_hcv Weighted average [trf_gr_ hcv] by
%Growth HCV link_s_len [link_s_len] where [ctype_onrc] = “SC”
Secondary ctype_onrc
Collector
Classification
Average % trf_gr_hcv Weighted average [trf_gr_ hcv] by
%Growth HCV link_s_len [link_s_len] where [ctype_onrc] = “ACC” or
Access ctype_onrc “ALV”
Classification
Sealed Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Roads Sealed psurf_stat and [ctype_onrc] = “NAT” or “NHV” and
Pavement ctype_onrc [cond_vis] = “1”
Condition cond_vis
National (repeat for [cond_vis] = 2, 3, 4 and 5)
Classification
Average Visual km link_s_len Sum of [link_s_len] where
Sealed psurf_stat [psurf_stat] = “S” and [ctype_onrc] = “REG”
Pavement ctype_onrc and [cond_vis] = “1”
Condition cond_vis
Regional (repeat for [cond_vis] = 2, 3, 4 and 5)
Classification
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Sealed psurf_stat and [ctype_onrc] = “ART” and [cond_vis] =
Pavement ctype_onrc “1”
Condition Arterial cond_vis
Classification (repeat for [cond_vis] = 2, 3, 4 and 5)
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Sealed psurf_stat and [ctype_onrc] = “PC” and [cond_vis] = “1”
Pavement ctype_onrc
Condition cond_vis (repeat for [cond_vis] = 2, 3, 4 and 5)
Primary Collector
Classification
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Condition Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Profile Sealed psurf_stat and [ctype_onrc] = “SC” and [cond_vis] = “1”
Pavement ctype_onrc
(using Condition cond_vis (repeat for [cond_vis] = 2, 3, 4 and 5)
visually Secondary
assessed Collector
data) Classification
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “S”
Sealed psurf_stat and [ctype_onrc] = “ACC” or “ALV” and
Pavement ctype_onrc [cond_vis] = “1”
Condition Access cond_vis
Classification (repeat for [cond_vis] = 2, 3, 4 and 5)
Unsealed Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Roads Unsealed psurf_stat and [ctype_onrc] = “NAT” or “NHV” and
Pavement ctype_onrc [cond_vis] = “1”
Condition cond_vis
National (repeat for [cond_vis] = 2, 3, 4 and 5)
Classification
Average Visual km link_s_len Sum of [link_s_len] where
Unsealed psurf_stat [psurf_stat] = “U” and [ctype_onrc] = “REG”
Pavement ctype_onrc and [cond_vis] = “1”
Condition cond_vis
Regional (repeat for [cond_vis] = 2, 3, 4 and 5)
Classification
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Unsealed psurf_stat and [ctype_onrc] = “ART” and [cond_vis] =
Pavement ctype_onrc “1”
Condition Arterial cond_vis
Classification (repeat for [cond_vis] = 2, 3, 4 and 5)
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Unsealed psurf_stat and [ctype_onrc] = “PC” and [cond_vis] = “1”
Pavement ctype_onrc
Condition cond_vis (repeat for [cond_vis] = 2, 3, 4 and 5)
Primary Collector
Classification
Average Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Unsealed psurf_stat and [ctype_onrc] = “SC” and [cond_vis] = “1”
Pavement ctype_onrc
Condition cond_vis (repeat for [cond_vis] = 2, 3, 4 and 5)
Secondary
Collector
Classification
Profile Visual km link_s_len Sum of [link_s_len] where [psurf_stat] = “U”
Unsealed psurf_stat and [ctype_onrc] = “ACC” or “ALV” and
Pavement ctype_onrc [cond_vis] = “1”
Condition Access cond_vis
Classification (repeat for [cond_vis] = 2, 3, 4 and 5)
Bridges Timber Bridge m br_len Sum of [br_len] where [br_dek_mat] =
Condition br_dek_mat “timber” and [br_cond] = “1”
br_cond
(repeat for [br_cond] = 2, 3 and 4)
Other Bridge m br_len Sum of [br_len] where [br_dek_mat] ≠
Condition br_dek_mat “timber” and [br_cond] = “1”
br_cond
(repeat for [br_cond] = 2, 3 and 4)
Tunnels Lined Tunnel m tun_len Sum of [tun_len] where [tun_serv] = “S” and
Condition tun_serv [cond_vis] = “1”
cond_vis
(repeat for [br_cond] = 2, 3, 4 and 5)
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Tunnels Unlined Tunnel m tun_len Sum of [tun_len] where [tun_serv] = “U” and
(continued) Condition tun_serv [cond_vis] = “1”
cond_vis
(repeat for [br_cond] = 2, 3, 4 and 5)
Condition Sealed Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “NAT”
Profile Roads Measured ctype_onrc or “NHV” and [iri_lane] “>2.3 and <=3.1”
(Roughness Sealed
(using ) Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
machine Roughness and <=4.6, >4.6 and <=5.3, >5.3)
measured National
data) Classification
Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “REG”
Measured ctype_onrc and [iri_lane] “>2.3 and <=3.1”
Sealed
Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
Roughness and <=4.6, >4.6 and <=5.3, >5.3)
Regional
Classification
Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “ART”
Measured ctype_onrc and [iri_lane] “>2.3 and <=3.1”
Sealed
Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
Roughness and <=4.6, >4.6 and <=5.3, >5.3)
Arterial
Classification
Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “PC”
Measured ctype_onrc and [iri_lane] “>2.3 and <=3.1”
Sealed
Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
Roughness and <=4.6, >4.6 and <=5.3, >5.3)
Primary Collector
Classification
Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “SC”
Measured ctype_onrc and [iri_lane] “>2.3 and <=3.1”
Sealed
Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
Roughness and <=4.6, >4.6 and <=5.3, >5.3)
Secondary
Collector
Classification
Average km iri_lane Sum of [iri_lane] where [ctype_onrc] = “ACC
Measured ctype_onrc or “ALV” and [iri_lane] “>2.3 and <=3.1”
Sealed
Pavement (repeat for [iri_lane] >3.1 and <=3.8, >3.8
Roughness and <=4.6, >4.6 and <=5.3, >5.3)
Access
Classification
Sealed Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Roads Measured rut_iwp [ctype_onrc] = “NAT” or “NHV” and [rut_xxx]
(Rutting) Sealed ctype_onrc “>10 and <=15”
Pavement
Rutting National (repeat for [rut_xxx] >15 and <=20, >20 and
Classification <=25, >25 and <=30, >30)
Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Measured rut_iwp [ctype_onrc] = “REG” and [rut_xxx] “>10 and
Sealed ctype_onrc <=15”
Pavement
Rutting Regional (repeat for [rut_xxx] >15 and <=20, >20 and
Classification <=25, >25 and <=30, >30)
PHS Data
Reporting Category Measure Item Unit Application Algorithm for Reporting
Item(s)
Condition Sealed Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Profile Roads Measured rut_iwp [ctype_onrc] = “ART” and [rut_xxx] “>10 and
(Rutting) Sealed ctype_onrc <=15”
(using (continued) Pavement
machine Rutting Arterial (repeat for [rut_xxx] >15 and <=20, >20 and
measured Classification <=25, >25 and <=30, >30)
data)
(continued) Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Measured rut_iwp [ctype_onrc] = “PC” and [rut_xxx] “>10 and
Sealed ctype_onrc <=15”
Pavement
Rutting Primary (repeat for [rut_xxx] >15 and <=20, >20 and
Collector <=25, >25 and <=30, >30)
Classification
Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Measured rut_iwp [ctype_onrc] = “SC” and [rut_xxx] “>10 and
Sealed ctype_onrc <=15”
Pavement
Rutting (repeat for [rut_xxx] >15 and <=20, >20 and
Secondary <=25, >25 and <=30, >30)
Collector
Classification
Maximum mm rut_owp Max of [rut_owp] or [rut_iwp] where
Measured rut_iwp [ctype_onrc] = “ACC” or “ALV” and [rut_xxx]
Sealed ctype_onrc “>10 and <=15”
Pavement
Rutting Access (repeat for [rut_xxx] >15 and <=20, >20 and
Classification <=25, >25 and <=30, >30)
Financial All Assets Average Annual $ capex_ren [capex_ren]
Perform- Renewal
ance Expenditure
Average Annual $ opex_maint [opex_maint]
Maintenance
Expenditure
Average Annual $ opex_oper [opex_oper]
Operations
Expenditure
aadt_all Average annual Utilisation- 8.6.12 act1_date Actual date for Performance 8.10.7
daily traffic Traffic Performance (Asset)-
volumes actual Achievement
aadt_bke Percentage of Utilisation- 8.6.20 added_by Data editor Inventory-All - [Link]
aadt classified as Traffic C Additional
motorbike volumes
added_date Data added date Inventory-All - [Link]
aadt_bke_l Percentage of Utilisation- 8.6.21 C Additional
aadt per lane Traffic
classified as volumes advert Advertising on Inventory- [Link]
motorbike shelter Shelters
asset_stat Operation status Inventory-All - [Link] br_cel_typ Cell Type For Inventory- [Link]
B Valuation Major Culvert Bridge Major
Culvert
atsu_amp AM Peak Actual Performance 8.12.57
Travel Speed (Service)- br_clear Vertical Clearance Inventory- [Link]
(Urban) Travel Speed Bridge Major
Culvert
atsu_day All Day Actual Performance 8.12.60
Travel Speed (Service)- br_co_code Component code Inventory- [Link]
(Urban) Travel Speed Bridge Major
Culvert
atsu_off Off Peak Actual Performance 8.12.59
Travel Speed (Service)- br_co_len Length Inventory- [Link]
(Urban) Travel Speed Bridge Major
Culvert
atsu_pmp PM Peak Actual Performance 8.12.58
Travel Speed (Service)- br_co_mat Component Inventory- [Link]
(Urban) Travel Speed material Bridge Major
Culvert
att Actual Travel Performance 8.12.54
Time (Service)- br_co_type Component type Inventory- [Link]
Travel Speed Bridge Major
Culvert
avg_hei Average height Inventory- [Link]
Retaining br_col_mat Column or Pile Inventory- [Link]
Walls Material Bridge Major
Culvert
bays Bay number Inventory- [Link]
Parking br_col_no Number of Inventory- [Link]
columns or Piles Bridge Major
bcr Benefit cost ratio Works and 8.14.34 Culvert
Costs-Output
br_comps Number of Inventory- [Link]
beam_mat Beam Material Inventory- [Link] components Bridge Major
Bridge Major Culvert
Culvert
br_cond Bridge conditIon Condition- 8.4.83
bin_cap Capacity Inventory-Bins [Link] state overall Bridge
bin_liner Liner present Inventory-Bins [Link] br_cond_1 Bridge conditIon Condition- 8.4.79
state 1 Bridge
bin_manuf Manufacturer Inventory-Bins [Link]
br_cond_2 Bridge conditIon Condition- 8.4.80
bin_mat Material Inventory-Bins [Link]
state 2 Bridge
bin_model Model number Inventory-Bins [Link]
br_cond_3 Bridge conditIon Condition- 8.4.81
bin_suppl Supplier Inventory-Bins [Link] state 3 Bridge
br_fnd_typ Foundation type Inventory- [Link] bridge_pc Bridges replaced Performance 8.10.26
Bridge Major (Asset)-
Culvert Output
br_func Function of the Inventory- [Link] bus_route Is a Bus/Public Demand- 8.5.2
Feature Bridge Major Transport Route Design
Culvert
capex_ren Capital Spend – Performance 8.11.13
br_gate Entrance Gate Inventory- [Link] Renewals (Financial)-
Bridge Major Investment
Culvert
capex_tot Total Capital Performance 8.11.11
br_hei Height Inventory- [Link] Spend (Financial)-
Bridge Major Investment
Culvert
capex_ue Capital Spend – Performance 8.11.12
br_heritag State Or National Inventory- [Link] Upgrade and (Financial)-
Heritage Listing Bridge Major Expansion Investment
Culvert
cbox_typ Pedestrian call Inventory- [Link]
br_ld_lim Vehicular Load Inventory- [Link] box type Traffic Signals
Limit Bridge Major
Culvert cgi_amp AM Peak Performance 8.12.62
Congestion (Service)-
br_len Length Inventory- [Link] Indicator (Urban) Travel Speed
Bridge Major
Culvert cgi_day All Day Performance 8.12.65
Congestion (Service)-
br_pie_mat Pier Material Inventory- [Link] Indicator (Urban) Travel Speed
Bridge Major
Culvert cgi_off Off Peak Performance 8.12.64
Congestion (Service)-
br_pier_no Number of Piers Inventory- [Link] Indicator (Urban) Travel Speed
Bridge Major
Culvert cgi_pmp PM Peak Performance 8.12.63
Congestion (Service)-
br_rai_mat Safety Rail Inventory- [Link] Indicator (Urban) Travel Speed
Material Bridge Major
Culvert chip_large Largest Chip Inventory- [Link]
Pavement
br_rail Safety Rails Inventory- [Link] Surfacing
Present Bridge Major
Culvert chip_small Smallest chip size Inventory- [Link]
Pavement
br_spans Number of Spans Inventory- [Link] Surfacing
or Cells Bridge Major
Culvert clim_tmi Thornthwaite Condition- 8.4.11
Moisture Index Climate
br_struc Feature Structure Inventory- [Link]
Type Bridge Major coat_sys Coating system Inventory- [Link]
Culvert Road Barriers
br_wid_l Bridge Width Left Inventory- [Link] cond_date Subjective Condition- 8.4.2
of Centreline Bridge Major condition survey Subjective
Culvert date-time condition
br_wid_r Bridge Width Inventory- [Link] cond_ed Visual edge drop Condition- 8.4.8
Right of Centreline Bridge Major off Visually
Culvert assessed
condition
cond_subj Subjective Condition- 8.4.1 crash _p Total crash count Performance 8.12.37
condition Subjective (Population) (Service)-
condition Road Safety
cond_vis Visual assessed Condition- 8.4.4 crash _t Total crash count Performance 8.12.38
condition Visually (Vehicle- (Service)-
assessed Kilometres Road Safety
condition Travelled)
const_cost Construction cost Inventory-All - [Link] crash_date Crash date Performance 8.12.31
B Valuation (Service)-
Road Safety
const_date Construction date Inventory-All - [Link]
B Valuation crash_loc Crash location Performance 8.12.32
(Service)-
cont_id Contractor or Inventory-All - [Link] Road Safety
suppliers Unique A General
asset ID crash_r_us Road user Performance 8.12.33
involved (Service)-
cost_unit Unit cost Inventory-All - [Link] Road Safety
B Valuation
crash_sev Crash severity Performance 8.12.34
cr_all_ex All cracking extent Condition- 8.4.12 (Service)-
Pavement - Road Safety
Cracking
crash_yrs Crash count Performance 8.12.36
cr_all_sv All cracking Condition- 8.4.13 number of years (Service)-
severity Pavement - of data Road Safety
Cracking
crit_comp Critical Rating Criticality- 8.7.1
cr_croc_ex Crocodile/block Condition- 8.4.19 Output
cracking extent Pavement -
Cracking crit_conn Criticality Classification- 8.2.3
Economic and
cr_croc_sv Crocodile/block Condition- 8.4.18 Social
cracking severity Pavement -
Cracking cross_dep Vehicle crossing Inventory- [Link]
depth Vehicle
Crossings
cycl_user User Classification Utilisation- 8.6.3 drc Depreciated Works and 8.14.35
Bicycles replacement cost Costs-Output
dat_confid Data confidence Data Control- 7.2.4 drn_dep Table drain depth Inventory- [Link]
Data Control Table Drains
dat_date Data date Data Control- 7.2.1 drn_len Table drain length Inventory- [Link]
Data Control Table Drains
dat_edit Data edit date Data Control- 7.2.6 drn_mat Table drain Inventory- [Link]
Data Control material Table Drains
dat_editor Data editor Data Control- 7.2.5 drn_resp Authority Inventory- [Link]
Data Control responsible for Table Drains
maintenance
dat_owner Data owner Data Control- 7.2.2
Data Control drn_shape Table drain shape Inventory- [Link]
Table Drains
dat_source Data source Data Control- 7.2.3
Data Control drn_wid Table drain width Inventory- [Link]
Table Drains
dat_source Data source Inventory-All - A [Link]
General elec_cert Electrical Inventory- [Link]
Certification Public Art
defct_ligt Reported number Performance 8.12.19
of service issues (Service)- eq_rating Earthquake Rating Inventory- [Link]
for lighting Customer Tunnels
Safety
(Condition) esa Equivalent Demand- 8.5.1
Standard Axle Design
defct_num Reported number Performance 8.12.15
of defects (Service)- ESA_km Equivalent Demand- 8.5.6
Customer Standard Axles Road Use
Safety kilometres
(Condition) fen_func Function Inventory- [Link]
defct_path Reported number Performance 8.12.16 Fences
of defects on (Service)- fen_hei Height Inventory- [Link]
pathways Customer Fences
Safety
(Condition) fen_joint Joint ownership Inventory- [Link]
Fences
defct_rail Reported number Performance 8.12.18
of service issues (Service)- fen_len Length Inventory- [Link]
for traffic Customer Fences
restraining Safety
devices (Condition) fen_manuf Manufacturers Inventory- [Link]
name Fences
defct_surf Reported number Performance 8.12.17
of defects on (Service)- fen_mat Material Inventory- [Link]
pavement surface Customer Fences
Safety
(Condition) fen_prot Drop protection Inventory- [Link]
Fences
design_co Design Company Inventory-All - [Link]
name A General fen_typ Type Inventory- [Link]
Fences
design_esa Design ESA Inventory- [Link]
Pavement All fin_arfr Asset Renewal Performance 8.11.9
Funding Ratio (Financial)-
donated_by Donated by Inventory- [Link] Financial
Public Art
fin_asr Asset Performance 8.11.10
dr_liner Type of drainage Inventory- [Link] Sustainability (Financial)-
liner Slopes Ratio Financial
fin_osr Operating Surplus Performance 8.11.7 hazards Reported number Performance 8.12.14
Ratio (Financial)- of hazards (Service)-
Financial Customer
Safety
found_mat Bank foundation Inventory- [Link] (Condition)
material Slopes
hospitals Hospital Access Classification- 8.2.8
found_mat Foundation Inventory- [Link] Road Economic and
material Structures Social
found_typ Foundation type Inventory- [Link] hr_vol Number of Utilisation- 8.6.17
Retaining vehicles per hour Traffic
Walls volumes
fr_sig_val Freight value in Classification- 8.2.4 inc_r_time Time to respond Performance 8.12.70
motion Economic and to incident (Service)-
Social Unplanned
Incidents
fr_sig_wgt Freight weight in Classification- 8.2.5
motion Economic and int_type Intersection Utilisation- 8.6.4
Social control type Capacity
fwp_cest Forward works Works and 8.14.8 iri_date Roughness survey Condition- 8.4.36
treatment Costs-FWP date-time Pavement -
estimated cost Roughness
fwp_cost_a Forward work Works and 8.14.31 iri_iwp Inner wheel path Condition- 8.4.34
treatment actual Costs-Output roughness Pavement -
completed cost Roughness
fwp_end Forward works Works and 8.14.5 iri_lane Lane roughness Condition- 8.4.33
program treatment Costs-FWP quarter car Pavement -
location end Roughness
fwp_end_yr Planned forward Works and 8.14.9 iri_name Roughness survey Condition- 8.4.37
treatment end Costs-FWP operator Pavement -
year Roughness
fwp_param Forward work Works and 8.14.6 iri_owp Outer wheel path Condition- 8.4.35
program Costs-FWP roughness Pavement -
intervention Roughness
parameter
its_abobel Above or below Inventory-ITS [Link]
fwp_reason Forward works Works and 8.14.2 surface level Assets
program treatment Costs-FWP
reason its_access Access Inventory-ITS [Link]
requirements Assets
fwp_start Forward works Works and 8.14.4
program treatment Costs-FWP its_l_clen Conduit material Inventory-ITS [Link]
location start Line
fwp_thresh Forward work Works and 8.14.7 its_l_cnid Controller ID Inventory-ITS [Link]
program Costs-FWP Line
intervention
threshold its_l_coid Contractors Inventory-ITS [Link]
unique ID Line
fwp_treat Forward works Works and 8.14.1
program category Costs-FWP its_l_dl Design life Inventory-ITS [Link]
Line
fwp_yr_s Planned forward Works and 8.14.3
work treatment Costs-FWP its_l_ints Installer Inventory-ITS [Link]
start year Line
geotextile Geotextile Fabric Inventory- [Link] its_l_len Conduit length Inventory-ITS [Link]
used Slopes Line
GVM_km Gross Vehicle Demand- 8.5.5 its_l_liae Defects liability Inventory-ITS [Link]
Mass kilometres Road Use end date Line
l_led_manu LED chip Inventory- [Link] life_rem_c Remaining life Performance 8.10.17
manufacturer Lighting calculated (Asset)-Asset
Life
l_lum_num Number of Inventory- [Link]
luminaires Lighting life_rem_m Remaining life Performance 8.10.18
calculation (Asset)-Asset
l_manu_imp Manufacturer Inventory- [Link] method Life
Importer name Lighting
life_use_a Useful life Performance 8.10.9
l_manuf Luminaire Inventory- [Link] assessed (Asset)-Asset
manufacturer Lighting Life
l_model Luminaire model Inventory- [Link] life_use_c Useful life Performance 8.10.10
type Lighting calculated (Asset)-Asset
Life
l_power_co Power supply Inventory- [Link]
company Lighting life_use_m Useful life Performance 8.10.11
calculation (Asset)-Asset
l_shd_typ Light shade type Inventory- [Link] method Life
Lighting
lin_app_r Application Rate Inventory- [Link]
l_smart_gd Connected to Inventory- [Link] Linemarking
smart grid Lighting All
l_tilt_ang Upcast angle Inventory- [Link] lin_aud Audible Inventory- [Link]
Lighting Linemarking
All
link_id Link ID Network-Link 8.1.9 loc_e_si side of road end Location [Link]
Referencing-
link_len Link length Network-Link 8.1.11 Polyline
link_s_e Link section end Network-Link 8.1.21 loc_l_e End location left Location [Link]
displacement Section Referencing-
Polygon
link_s_id Link section ID Network-Link 8.1.19
Section loc_l_e_of End lateral offset Location [Link]
left Referencing-
link_s_len Link section length Network-Link 8.1.22 Polygon
Section
loc_l_s Start location left Location [Link]
link_s_s Link section start Network-Link 8.1.20 Referencing-
displacement Section Polygon
link_s_uni Link section Network-Link 8.1.24 loc_l_s_of Start lateral offset Location [Link]
uniform width Section left Referencing-
link_s_wid Link section Network-Link 8.1.23 Polygon
average width Section loc_offset Offset Location [Link]
link_tflow Link traffic flow Network-Link 8.1.10 Referencing-
Point
links_div Separate link Network-Link 8.1.31
sections for traffic Section loc_proj Projection Location [Link]
flow direction Referencing-
Point
links_lanl Number of lanes Network-Link 8.1.27
left of centreline Section loc_proj Projection Location [Link]
Referencing-
Polyline
loc_r_e End location right Location [Link] loc_x_s_l X coordinate start Location [Link]
Referencing- left Referencing-
Polygon Polygon
loc_r_e_of End lateral offset Location [Link] loc_x_s_r X coordinate start Location [Link]
right Referencing- right Referencing-
Polygon Polygon
loc_r_s Start location right Location [Link] loc_y Y coordinate Location [Link]
Referencing- Referencing-
Polygon Point
loc_r_s_of Start lateral offset Location [Link] loc_y_e Y coordinate end Location [Link]
right Referencing- Referencing-
Polygon Polyline
loc_s Start location Location [Link] loc_y_e_l Y coordinate end Location [Link]
Referencing- left Referencing-
Polyline Polygon
loc_s_si Side of road start Location [Link] loc_y_e_r Y coordinate end Location [Link]
Referencing- right Referencing-
Polyline Polygon
loc_side Side Location [Link] loc_y_s Y coordinate start Location [Link]
Referencing- Referencing-
Point Polyline
loc_vert Vertical datum Location [Link] loc_y_s_l Y coordinate start Location [Link]
Referencing- left Referencing-
Point Polygon
loc_vert Vertical datum Location [Link] loc_y_s_r Y coordinate start Location [Link]
Referencing- right Referencing-
Polyline Polygon
loc_wid_e End width Location [Link] loc_z_e Z coordinate end Location [Link]
Referencing- Referencing-
Polyline Polyline
loc_wid_s Start width Location [Link] loc_z_e_l Z coordinate end Location [Link]
Referencing- left Referencing-
Polyline Polygon
loc_x_e X coordinate end Location [Link] loc_z_s Z coordinate start Location [Link]
Referencing- Referencing-
Polyline Polyline
loc_x_e_l X coordinate end Location [Link] loc_z_s_l Z coordinate start Location [Link]
left Referencing- left Referencing-
Polygon Polygon
loc_x_e_r X coordinate end Location [Link] loc_z_s_r Z coordinate start Location [Link]
right Referencing- right Referencing-
Polygon Polygon
me_supp Supplier Inventory- [Link] mt_dlp_e Defect liability end Works and 8.14.19
Mechanical date Costs-
and Electrical Maintenance
Point
mt_dlp_s Defect liability Works and 8.14.18
me_typ Type Inventory- [Link] start date Costs-
Mechanical Maintenance
and Electrical
Assets mt_id Source Works and 8.14.20
Identification Costs-
me_ups UPS is connected Inventory- [Link] Maintenance
Mechanical
and Electrical mt_int_par Intervention Works and 8.14.23
Point parameter Costs-
Maintenance
me_warrend Warranty end date Inventory- [Link]
Mechanical mt_int_thr Intervention Works and 8.14.24
and Electrical threshold Costs-
Point Maintenance
meter Metered parking Inventory- [Link] mt_loc Location reference Works and 8.14.27
Parking type Costs-
Maintenance
mt_act Work activity Works and 8.14.29
Costs- mt_quan Work quantity Works and 8.14.14
Maintenance Costs-
Maintenance
mt_act_grp Activity group Works and 8.14.28
Costs- mt_ref Source Works and 8.14.21
Maintenance Identification Costs-
Reference Maintenance
mt_action Action completed Works and 8.14.25
Costs- mt_status Status of work Works and 8.14.12
Maintenance Costs-
Maintenance
mt_compl Date and time of Works and 8.14.26
completion Costs- mt_unit Unit for payment Works and 8.14.13
Maintenance Costs-
Maintenance
mt_cost Maintenance paid Works and 8.14.16
amount Costs- mtt Mean Travel Time Performance 8.12.55
Maintenance (Service)-
Travel Speed
mt_crate Work schedule Works and 8.14.15
rate Costs- network_na Network Name Network- 8.1.1
Maintenance Network
mt_cyc Maintenance cycle Works and 8.14.30 no_str_bri Number of Bridge Network-Road 8.1.17
Costs- Structures
Maintenance
no_str_cul Number of Major Network-Road 8.1.18
mt_date_a Date approved for Works and 8.14.17 Culvert Structures
payment Costs-
no_str_tot Number of Major Network-Road 8.1.16
Maintenance
Structures
mt_date_cr Date and time of Works and 8.14.22
node_id Node ID Network-Node 8.1.2
creation Costs-
Maintenance node_x_e X coordinate end Network-Node 8.1.6
Node
mt_def Defect description Works and 8.14.11
Costs- node_x_s X coordinate start Network-Node 8.1.3
Maintenance node
mt_def_id Maintenance Works and 8.14.10 node_y_e Y coordinate end Network-Node 8.1.7
defect ID Costs- Node
Maintenance
node_y_s Y coordinate start Network-Node 8.1.4
node
node_z_e Z coordinate end Network-Node 8.1.8 p_df_name Deflection survey Condition- 8.4.32
Node operator Pavement -
Deflection
node_z_s Z coordinate start Network-Node 8.1.5
node p_df_veh Deflection testing Condition- 8.4.22
vehicle Pavement -
ntsu Nominal Travel Performance 8.12.61 Deflection
Speed (Urban) (Service)-
Travel Speed p_lay_cbr layer CBR Inventory- [Link]
Pavement
ntt Nominal Travel Performance 8.12.53
Time (Service)- p_lay_dep Layer depth Inventory- [Link]
Travel Speed Pavement
operator Operator Network-Link 8.1.36 p_lay_mat Layer material Inventory- [Link]
organisation Section Pavement
opex_dep Depreciation Performance 8.11.17 p_lay_no Layer number Inventory- [Link]
Expense (Financial)- Pavement
Investment
p_lay_stab Layer Stabilising Inventory- [Link]
opex_maint Recurrent Spend Performance 8.11.15 agent Pavement
– Maintenance (Financial)-
Investment p_lay_typ Layer type Inventory- [Link]
Pavement
opex_oper Recurrent Spend Performance 8.11.16
– Operations (Financial)- p_lay_ucs layer UCS Inventory- [Link]
Investment Pavement
opex_tot Total Recurrent Performance 8.11.14 p_lay_wid Layer width Inventory- [Link]
Spend (Financial)- Pavement
Investment
p_recy_mat Recylced Material Inventory- [Link]
owner Owner of the asset Inventory-All - A [Link] Pavement All
General
p_recy_per Recycled Inventory- [Link]
owner Ownership Network-Link 8.1.35 Percentage Pavement All
organisation Section p_stab_pct Stabilising agent Inventory- [Link]
p_axle_max Load Limit Inventory- [Link] percent Pavement
Pavement All p_wid_l Lateral width left Inventory- [Link]
p_df_act Actual applied Condition- 8.4.28 Pavement All
load Pavement - p_wid_r Lateral width right Inventory- [Link]
Deflection Pavement All
p_df_d0 Pavement Condition- 8.4.23 paint_colo Paint colour Inventory- [Link]
deflection d0 Pavement - Road Barriers
Deflection
park_type Type Inventory- [Link]
p_df_d1500 Pavement Condition- 8.4.27 Parking
deflection d1500 Pavement -
Deflection path_b_dep BaseDepth Inventory- [Link]
Pathways
p_df_d200 Pavement Condition- 8.4.24
deflection d200 Pavement - path_b_typ BaseType Inventory- [Link]
Deflection Pathways
p_df_d300 Pavement Condition- 8.4.25 path_c_dep Depth Crossing Inventory- [Link]
deflection d300 Pavement - Pathways
Deflection
path_cond Pathway visual Condition- 8.4.89
p_df_d900 Pavement Condition- 8.4.26 condition Pathway/Foot
deflection d900 Pavement - paths
Deflection
path_date Pathways survey Condition- 8.4.90
p_df_date Deflection survey Condition- 8.4.31 date-time Pathway/Foot
date-time Pavement - paths
Deflection
pit_li_typ Lid Type Inventory-Pits [Link] psurf_stat Road surface Inventory- [Link]
status Pavement
pit_no Pit number Inventory-Pits [Link] Surfacing All
pit_st_typ Construction Type Inventory-Pits [Link] psv Polished Stone Inventory- [Link]
Value of Chip for Pavement
pit_steps Number of step Inventory-Pits [Link]
the seal layer Surfacing
irons
pt_reliab Public transport Performance 8.12.29
pit_trap Litter trap type Inventory-Pits [Link]
reliability (Service)-
pit_typ Type Inventory-Pits [Link] Public
Transport
pit_x X Coordinate Inventory-Pits [Link]
purpose Purpose Inventory- [Link]
pit_y Y Coordinate Inventory-Pits [Link] Parking
plan_no As Constructed Inventory-All - [Link] rb_attach Attachments on Inventory- [Link]
Plan Number A General the barrier Road Barriers
plaque_des Plaque description Inventory- [Link] rb_end_typ Barrier End style Inventory- [Link]
Public Art Road Barriers
plaque_yr Plate or plaque Inventory- [Link] rb_grn_fix Ground fixed Inventory- [Link]
year Tunnels method Road Barriers
pofoun_mat Foundation Inventory- [Link] rb_hei Height of barrier Inventory- [Link]
material Poles Road Barriers
pole_attac Pole attachments Inventory- [Link] rb_len Length of barrier Inventory- [Link]
present Poles Road Barriers
pole_cntrl Pole controller Inventory- [Link] rb_mod_no Model number Inventory- [Link]
Poles Road Barriers
pole_earth Pole earth Inventory- [Link] rb_offset Lateral offset face Inventory- [Link]
method Poles Road Barriers
pole_finsh Pole finish Inventory- [Link] rb_pos_mat Material barrier Inventory- [Link]
Poles posts Road Barriers
pole_found Foundation type Inventory- [Link] rb_posts Barrier number of Inventory- [Link]
Poles posts Road Barriers
pole_hei Pole height Inventory- [Link] rb_rai_mat Material barrier Inventory- [Link]
Poles rail. Road Barriers
pole_manuf Pole Manufacturer Inventory- [Link] rb_styl_e Barrier end style Inventory- [Link]
Poles Road Barriers
pole_mat Pole Material Inventory- [Link] rb_styl_s Barrier start style Inventory- [Link]
Poles Road Barriers
pole_model Pole model Inventory- [Link] rb_typ Road barrier type Inventory- [Link]
number Poles Road Barriers
pole_stand Design Standard Inventory- [Link] rb_typ_s Barrier start type Inventory- [Link]
Poles Road Barriers
pole_typ Pole type Inventory- [Link] rb_wid Rail width Inventory- [Link]
Poles Road Barriers
pop Estimated Classification- 8.2.2 rce_1to2 Return on Performance 8.11.2
population served Economic and Construction (Financial)-
by road Social Expenditure BCR Development
1-2 Program /
pop_catch Population Demand- 8.5.3 Project
Population Assessment
prm Percent routine Works and 8.14.33 rce_2to3 Return on Performance 8.11.3
maintenance Costs-Output Construction (Financial)-
risk_mo_dt Schedule Risk- 8.8.10 rut_iwp_X0 Rut depth inner Condition- 8.4.49
monitoring plan Monitoring wheel path Pavement -
review date >40mm Rutting
risk_mo_id Montioring plan Risk- 8.8.11 rut_lane Rut depth lane Condition- 8.4.38
identifier Monitoring Pavement -
Rutting
risk_rate Risk Rating Risk-Output 8.8.12
Overall rut_name Rutting survey Condition- 8.4.62
operator Pavement -
rme Routine Works and 8.14.32 Rutting
maintenance Costs-Output
efficiency rut_owp Rut depth outer Condition- 8.4.50
Pavement -
road_from Chainage at start Inventory- [Link] Rutting
of street segment Pavement All
rut_owp_10 Rut depth outer Condition- 8.4.53
road_id Road ID Network-Road 8.1.12 wheel path >5mm- Pavement -
<10mm Rutting
road_len Road Length Network-Road 8.1.14
rut_owp_15 Rut depth outer Condition- 8.4.54
road_name Road name Network-Road 8.1.13
wheel path Pavement -
road_to Chainage at end Inventory- [Link] >10mm-<15mm Rutting
of street segment Pavement All
rut_owp_20 Rut depth outer Condition- 8.4.55
rut_date Rutting survey Condition- 8.4.61 wheel path >15- Pavement -
date-time Pavement - <20mm Rutting
Rutting
rut_owp_25 Rut depth outer Condition- 8.4.56
rut_iwp Rut depth inner Condition- 8.4.39 wheel path >20- Pavement -
Pavement - <25mm Rutting
Rutting
rut_owp_30 Rut depth outer Condition- 8.4.57
rut_iwp_10 Rut depth inner Condition- 8.4.42 wheel path >25- Pavement -
wheel path >5mm- Pavement - <30mm Rutting
<10mm Rutting
rut_owp_35 Rut depth outer Condition- 8.4.58
rut_iwp_15 Rut depth inner Condition- 8.4.43 wheel path >30- Pavement -
wheel path Pavement - <35mm Rutting
>10mm-<15mm Rutting
rut_owp_40 Rut depth outer Condition- 8.4.59
rut_iwp_20 Rut depth inner Condition- 8.4.44 wheel path >35- Pavement -
wheel path >15- Pavement - <40mm Rutting
<20mm Rutting
rut_owp_5 Rut depth outer Condition- 8.4.52
rut_iwp_25 Rut depth inner Condition- 8.4.45 wheel path 0- Pavement -
wheel path >20- Pavement - <5mm Rutting
<25mm Rutting
rut_owp_sd Rut depth Condition- 8.4.51
rut_iwp_30 Rut depth inner Condition- 8.4.46 standard deviation Pavement -
wheel path >25- Pavement - inner Rutting
<30mm Rutting
rut_owp_X0 Rut depth outer Condition- 8.4.60
rut_iwp_35 Rut depth inner Condition- 8.4.47 wheel path Pavement -
wheel path >30- Pavement - >40mm Rutting
<35mm Rutting
rw_above Features above Inventory- [Link]
rut_iwp_40 Rut depth inner Condition- 8.4.48 the wall Retaining
wheel path >35- Pavement - Walls
<40mm Rutting
rw_below Features below Inventory- [Link]
rut_iwp_5 Rut depth inner Condition- 8.4.41 the wall Retaining
wheel path 0- Pavement - Walls
<5mm Rutting
rw_fac_are Face area of wall Inventory- [Link]
rut_iwp_sd Rut depth Condition- 8.4.40 Retaining
standard deviation Pavement - Walls
inner Rutting
rw_fac_mat Face material Inventory- [Link] s_bind_typ Binder type Inventory- [Link]
Retaining Pavement
Walls Surfacing
rw_fac_thi Face thickness Inventory- [Link] s_cut Cutter Quantity Inventory- [Link]
Retaining Pavement
Walls Surfacing
rw_len Length of retaining Inventory- [Link] s_cut_typ Cutter type Inventory- [Link]
wall Retaining Pavement
Walls Surfacing
rw_max_hei Maximum height Inventory- [Link] s_dep Depth of the seal Inventory- [Link]
Retaining Pavement
Walls Surfacing
rw_offset Lateral offset face Inventory- [Link] s_elas_rec Elastic recovery Inventory- [Link]
Retaining Pavement
Walls Surfacing
rw_pos_mat Wall post material Inventory- [Link] s_flux Quantity of flux Inventory- [Link]
Retaining Pavement
Walls Surfacing
rw_restrai Restraining Inventory- [Link] s_func Seal layer function Inventory- [Link]
mechanism of the Retaining Pavement
asset Walls Surfacing
rw_tie_row Number of Inventory- [Link] s_lay_no The surface layer Inventory- [Link]
anchorage rows Retaining number Pavement
Walls Surfacing
rw_tie_sys Anchoring system Inventory- [Link] s_life_des Design life Inventory- [Link]
Retaining Pavement
Walls Surfacing All
rw_tilt Back tilt angle Inventory- [Link] s_mat Surfacing material Inventory- [Link]
Retaining type Pavement
Walls Surfacing
s_add_quan Additive quantity Inventory- [Link] s_ply_typ Polymer type Inventory- [Link]
Pavement Pavement
Surfacing Surfacing
saferisk_c Collective Road Performance 8.12.51 sf_t Road Fatalities Performance 8.12.44
Safety Risk (Service)- (Vehicle- (Service)-
Road Safety Kilometres Road Safety
Travelled)
saferisk_p Personal Road Performance 8.12.52
Safety Risk (Service)- sfc_date SCRIM survey Condition- 8.4.66
Road Safety time-date Pavement
Surface - Skid
scc Number of Performance 8.12.39
Serious Casualty (Service)- sfc_iwp SCRIM inner Condition- 8.4.64
Crashes Road Safety wheel path Pavement
Surface - Skid
scc_p Serious Casualty Performance 8.12.40
Crashes (Service)- sfc_owp SCRIM outer Condition- 8.4.65
(Population) Road Safety wheel path Pavement
Surface - Skid
scc_t Serious Casualty Performance 8.12.41
Crashes (Vehicle- (Service)- sfc_speed SCRIM speed Condition- 8.4.63
Kilometres Road Safety Pavement
Travelled) Surface - Skid
sci_path Pathways meeting Performance 8.12.20 sfc_veh SCRIM vehicle Condition- 8.4.67
the level of service (Service)- Pavement
standard Customer Surface - Skid
Safety
(Condition) sh_dis_acc Disabled access Inventory- [Link]
available Shelters
sci_pave Pavement Performance 8.12.21
Surfacing meeting (Service)- sh_flr_mat Floor material Inventory- [Link]
the level of service Customer Shelters
standard Safety
sh_manuf Shelter Inventory- [Link]
(Condition)
manufacturer Shelters
sdtt Standard Performance 8.12.56
sh_model Model number of Inventory- [Link]
Deviation of (Service)-
shelter Shelters
Travel Times Travel Speed
sh_roo_mat Roof material Inventory- [Link]
seal_len Length of seal Inventory- [Link]
Shelters
Pavement
Surfacing All sh_typ Shelter type Inventory- [Link]
Shelters
seal_spec Seal specification Inventory- [Link]
Pavement sh_wal_mat Wall material Inventory- [Link]
Surfacing All Shelters
seal_wid Width of seal Inventory- [Link] sign_angle Sign angle Inventory- [Link]
Pavement Signs
Surfacing All
sign_b_mat Background Inventory- [Link]
seal_year Year of current Inventory- [Link] material Signs
surface installation Pavement
Surfacing All sign_bcol Background Inventory- [Link]
colour Signs
seat_mat Seating material Inventory- [Link]
Shelters sign_frame Frame material Inventory- [Link]
Signs
seg_cl_len Centreline Inventory- [Link]
segment length Pavement All sign_elev Ground height Inventory-Signs [Link]
sign_panel Number of sign Inventory- [Link] slope_plan Planting exists Inventory- [Link]
panels Signs Slopes
sign_posts Number of posts Inventory- [Link] slope_rein Slope is reinforced Inventory- [Link]
Signs Slopes
sign_refno Local Sign Inventory- [Link] slope_seis Slope seismic Inventory- [Link]
Reference Signs rating Slopes
Number
slope_typ Slope in cut or fill Inventory- [Link]
sign_refsd Australian Inventory- [Link] Slopes
Standard Signs
Reference smart_pad Signal connected Inventory- [Link]
to a smart pad Traffic Signals
sign_stren Strengthening bar Inventory- [Link]
present Signs speed_85 85% Speed Utilisation- 8.6.5
Capacity
sign_supp Support type Inventory- [Link]
Signs sph Number of Performance 8.12.45
Persons (Service)-
sign_typ Sign Type Inventory- [Link] Hospitalised Road Safety
Signs
sph_p Persons Performance 8.12.46
sign_wid Width of sign Inventory- [Link] Hospitalised (Service)-
Signs (Population) Road Safety
sign_wordc Legend colour Inventory- [Link] sph_t Persons Performance 8.12.47
Signs Hospitalised (Service)-
(Vehicle- Road Safety
sign_wordm Legend material Inventory- [Link] Kilometres
Signs Travelled)
sign_words Wording on sign Inventory- [Link] sreq_compl Service request Performance 8.12.23
Signs response time (Service)-
compliance Customer
signal_hei Ground height to Inventory- [Link]
Safety
bottom of signal Traffic Signals
(Condition)
sk_res_20 Skid resistance Condition- 8.4.69
sreq_time Achieved service Performance 8.12.22
20m Pavement
request response (Service)-
Surface - Skid
time Customer
sk_res_50 Skid resistance Condition- 8.4.70 Safety
50m Pavement (Condition)
Surface - Skid
ssc Social Cost of Performance 8.12.48
skid_test Skid Resistance Condition- 8.4.68 Serious Casualty (Service)-
Test Pavement Crash Road Safety
Surface - Skid
ssc_p Social Cost of Performance 8.12.49
slope_area Area of slope face Inventory- [Link] Serious Casualty (Service)-
Slopes Crashes Road Safety
(Population)
slope_drn Active or passive Inventory- [Link]
drainage Slopes ssc_t Social Cost of Performance 8.12.50
Serious Casualty (Service)-
slope_grad Gradient of batter Inventory- [Link] Crashes (Vehicle- Road Safety
slope Slopes Kilometres
Travelled)
slope_hei Average height Inventory- [Link]
Slopes sseal_pc Spray seal Performance 8.10.22
resurfacing (Asset)-
slope_len Slope length Inventory- [Link] coverage across Output
Slopes sealed network
slope_mon Geotechnical Inventory- [Link] stage_no Subdivision stage Inventory-All - [Link]
monitoring Slopes or project number A General
equipment
ste_u_533 Smooth Travel Performance 8.12.11 tboard_wid Target board Inventory- [Link]
Exposure Urban (Service)- width Traffic Signals
(5.33 IRI) Customer
temp_air Ambient air Condition- 8.4.29
Experience
temperature Pavement -
struc_att Structure Inventory- [Link] Deflection
attachments Structures
temp_pave Pavement Condition- 8.4.30
struc_fin Structure surface Inventory- [Link] temperature Pavement -
finish Structures Deflection
tm_model Model number Inventory- [Link] tree_roots Tree environment Inventory- [Link]
Traffic for roots Trees
Management
Devices Point tree_sig Tree significance Inventory- [Link]
Trees
tm_p_typ Traffic Inventory- [Link]
Management Traffic tree_speci Tree species Inventory- [Link]
Point Type Management Trees
Devices Point
tree_stat Tree Endemic Inventory- [Link]
tm_typ Traffic Inventory- [Link] status Trees
management Traffic
tree_stock Stock type Inventory- [Link]
device type Management
Trees
Devices
Polygon tree_supp Support type for Inventory- [Link]
tree Trees
tourism Tourist route Classification- 8.2.7
Economic and tree_wires Overhead wires Inventory- [Link]
Social present Trees
traf_cl_sy Traffic Utilisation- 8.6.14 trf_gr_all Annual growth (% Demand- 8.5.8
classification used Traffic / year) of all Traffic Growth
volumes vehicle classes
traf_class Traffic Utilisation- 8.6.15 trf_gr_bus Annual growth (% Demand- 8.5.10
classification Traffic / year) of all buses Traffic Growth
system class volumes
number trf_gr_cyc Annual growth (% Demand- 8.5.12
/ year) of cycles Traffic Growth
traf_dir Traffic flow Network-Link 8.1.32
direction Section trf_gr_hcv Annual growth (% Demand- 8.5.11
/ year) of all heavy Traffic Growth
traf_set Traffic setting Network-Link 8.1.33 vehicles
Section
trf_gr_lcv Annual growth (% Demand- 8.5.9
treat_e_a Actual work Works and 8.14.37 / year) of all light Traffic Growth
treatment end Costs-Output vehicles
date
ts_access Access to asset Inventory- [Link]
treat_s_a Actual work Works and 8.14.36 Traffic Signals
treatment start Costs-Output
date ts_attach Attachments type Inventory- [Link]
present on the Traffic Signals
tree_age Tree Age Inventory- [Link] poles
Trees
ts_callbox Pedestrian call Inventory- [Link]
tree_commo Common name Inventory- [Link] box present Traffic Signals
Trees
ts_cbmodel Call box model Inventory- [Link]
tree_dia Diameter of trunk Inventory- [Link] number Traffic Signals
Trees
ts_cont_id Controller ID Inventory- [Link]
tree_genus Genus Inventory- [Link] Traffic Signals
Trees
ts_cost Traffic signal Inventory- [Link]
tree_guard Tree guards Inventory- [Link] purchase cost Traffic Signals
present Trees
ts_cs_typ Control system Inventory- [Link]
tree_hei Height at capture Inventory- [Link] type Traffic Signals
Trees
ts_dat_log Data logger Inventory- [Link]
tree_maint Maintenance Inventory- [Link] present Traffic Signals
requirements Trees
ts_dl_sta Defects liability Inventory- [Link]
tree_metho Tree Planting Inventory- [Link] start date Traffic Signals
method Trees
ts_dlp_end Defects liability Inventory- [Link]
tree_prune Pruning time Inventory- [Link] end date Traffic Signals
interval Trees
ts_eth_typ Earthing type for Inventory- [Link] tun_ba_mat Barrel material Inventory- [Link]
signal pole Traffic Signals Tunnels
tx_date Texture survey Condition- 8.4.77 util_fut Future utilisation Utilisation- 8.6.9
date-time Pavement Output
Surface -
Texture util_mod Model name/ Utilisation- 8.6.7
version Output
tx_MPD_bwp MPD Pavement Condition- 8.4.76
texture between Pavement value Assessed cost in Inventory-All - [Link]
wheel path Surface - Australian/New B Valuation
Texture Zealand Dollars
tx_MPD_iwp MPD Pavement Condition- 8.4.74 value_type Valuation type Inventory-All - [Link]
texture inner Pavement B Valuation
wheel path Surface -
value_year Valuation year Inventory-All - [Link]
Texture
B Valuation
tx_MPD_owp MPD Pavement Condition- 8.4.75
veg_typ Vegetation type Inventory- [Link]
texture outer Pavement
planted Slopes
wheel path Surface -
Texture veh_hr_ln Number of Utilisation- 8.6.31
vehicles per lane Traffic
tx_name Texture survey Condition- 8.4.78
per hour volumes
operator Pavement
Surface - veh_p_h_ln Number of Utilisation- 8.6.30
Texture vehicles during Traffic
peak hour per volumes
tx_SMT_bwp SMTD Pavement Condition- 8.4.73
lane
texture between Pavement
wheel path Surface - vest_date Vesting date Inventory-All - [Link]
Texture C Additional
tx_SMT_iwp SMTD Pavement Condition- 8.4.71 vest_org Vesting source Inventory-All - [Link]
texture inner Pavement C Additional
wheel path Surface -
Texture video_det Video detection Inventory- [Link]
present Traffic Signals
tx_SMT_owp SMTD Pavement Condition- 8.4.72
texture outer Pavement visor_type Visor type Inventory- [Link]
wheel path Surface - Traffic Signals
Texture
vkt Vehicle Kilometers Demand- 8.5.4
us_date Unsealed survey Condition- 8.4.95 Travelled Road Use
date-time Unsealed
Roads vtt_amp AM Peak Performance 8.12.66
Variability of (Service)-
us_drain Unsealed Condition- 8.4.93 Travel Time Travel Speed
drainage condition Unsealed (Urban)
Roads
vtt_day All Day Variability Performance 8.12.69
us_gv_dep Gravel depth Condition- 8.4.94 of Travel Time (Service)-
Unsealed (Urban) Travel Speed
Roads
vtt_off Off Peak Performance 8.12.68
us_name Unsealed survey Condition- 8.4.96 Variability of (Service)-
operator Unsealed Travel Time Travel Speed
Roads (Urban)
Service Performance
Inventory incl. asset
Asset Performance
Activity
Classification
Connectivity
Condition
Demand
loc. Ref.
Access
Network Definition
Bridge Classification Y Y Y Y
Litigation Defence Y Y Y Y Y Y Y
Traffic Counting Y Y Y
Service Performance
Inventory incl. asset
Asset Performance
Activity
Classification
Connectivity
Condition
Demand
loc. Ref.
Access
Levels of Service Achievement (technical) Y Y Y Y
Traffic Planning Y Y Y Y
Traffic Predictions Y Y Y Y
Intersection Analysis Y Y Y Y Y
Service Requests Y Y Y
Service Performance
Inventory incl. asset
Asset Performance
Activity
Classification
Connectivity
Condition
Demand
loc. Ref.
Access
Defect Recording Y Y Y
Maintenance Management
Defect Repair Y Y Y
Crash Investigations Y Y Y Y Y Y
Asset Valuation Y Y Y Y Y Y Y
Funding Requests Y Y Y Y Y Y
Service Performance
Inventory incl. asset
Asset Performance
Activity
Classification
Connectivity
Condition
Demand
loc. Ref.
Access
Asset Demand Assessment Y Y Y Y
AM Policy Development Y
Asset Management
System (ISO55001)
SAMP Development Y Y Y Y Y Y Y Y Y
AM Objectives Development Y Y Y Y Y Y
AMP Development Y Y Y Y Y Y Y Y Y
SOP Development Y Y Y Y
Service Performance
Inventory incl. asset
Asset Performance
Activity
Classification
Connectivity
Condition
Demand
loc. Ref.
Access
Geometric Design Y Y Y
Development
Asset
Pavement Design Y Y Y Y Y Y Y
Surfacing Design Y Y Y Y Y Y