Data Quality Metric Library
CWAY1 - Road network data complete
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
8595
|
The percentage of the total network length, based on carriageway sections, where the map centreline length is within 10% of measured road length recorded in the carriageway table.
Metric Purpose
Check consistency between the 'measured' road length recorded in the carriageway table and the map centreline length.
Consequence of Poor Quality Data
Poor centreline data has the potential to impact the locational accuracy of data (inventory, maintenance activity, etc.) recorded in the field. Incorrect network length affects reported results including STE, VKT, etc. This also has the potential to impact investment decision making.
Changes for 2024/25:
CWAY1 is now an Information Only metric as the network centrelines for the RCA will be sourced from the AMDS Network Model.
CWAY2a - Rural number of lanes matches carriageway width
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Low | |
Grade thresholds |
8095
|
The percentage of the Rural sealed network length, based on carriageways, with an alignment between the recorded carriageway width and number of lanes. Alignments are as follows:
- Number of lanes = 1 and width < 6m,
- Number of lanes = 2 and width >4m or <17m,
- Number of lanes > 2 and width >9m.
Metric Purpose
Confirm that the number of lanes recorded for each rural carriageway relates to the recorded carriageway width.
Consequence of Poor Quality Data
Reduced understanding of traffic demand and loading on the network, and subsequently levels of service provided, network resilience, pavement and surfacing renewals forward works programming, etc.
Incorrect reporting of achieved lengths by lane-km in the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process for defining the number of lanes per carriageway section.
Specific comments on the metric
The width ranges were chosen by the project team to allow for exceptions that arise due to the varying nature of the networks across NZ. They are not necessarily in line with any design standards or best practice.
An example of a potential exception to this metric test is a carriageway with large areas of parking outside of the line of traffic.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
CWAY2b - Urban number of lanes matches carriageway width
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Low | |
Grade thresholds |
8095
|
The percentage of the Urban sealed network length, based on carriageways, with an alignment between the recorded carriageway width and number of lanes. Alignments are as follows:
- Number of lanes = 1 and width < 6m,
- Number of lanes = 2 and width >4m or <17m,
- Number of lanes > 2 and width >9m.
Metric Purpose
Confirm that the number of lanes recorded for each urban carriageway relates to the recorded carriageway width.
Consequence of Poor Quality Data
Reduced understanding of traffic demand and loading on the network, and subsequently levels of service provided, network resilience, pavement and surfacing renewals forward works programming, etc.
Incorrect reporting of achieved lengths by lane-km in the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process for defining the number of lanes per carriageway section.
Specific comments on the metric
The width ranges were chosen by the project team to allow for exceptions that arise due to the varying nature of the networks across NZ. They are not necessarily in line with any design standards or best practice.
An example of a potential exception to this metric test is a carriageway with large areas of parking outside of the line of traffic.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
CWAY4 - ONRC categories are assigned
Sub-category | Carriageway | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
9598
|
The proportion of the number of carriageway section records in the carriageway table with an assigned ONRC category.
Metric Purpose
Confirm that an ONRC category is recorded for all locally owned 'road' carriageway sections.
Consequence of Poor Quality Data
Parts of road network with no ONRC category are potentially excluded, or incorrectly defined, in planning, executing and reporting of maintenance and renewal activity.
Incorrect reporting of all ONRC Performance Measures results as parts of the network will not be included.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process or resources for the ongoing maintenance of this dataset. Lack of clarity or understanding that RCAs are expected to maintain their ONRC.
Specific comments on the metric
This metric only interrogates carriageways where the road is recorded with a local road type. Carparks recorded with a local road type are expected to 'fail' the test, and an allowance has been made for this in the grading ranges. Paths, walkways, and other parts of the network with a different road type have been excluded.
CWAY6a - Rural carriageways are generally not short
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Information Only | |
Grade thresholds |
7090
|
The proportion of the number of Rural sealed carriageway records with a length greater than 20m (ie. not short).
Metric Purpose
Confirm that the sectioning of rural carriageway lengths is appropriate.
Consequence of Poor Quality Data
Short carriageway sections can be difficult, and time consuming to manage and maintain.
Short carriageway sections have the potential to distort the reported results for the ONRC Amenity Performance Measures.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2020/21:
State Highway lengths are short if < 500m.
Changes for 2021/22:
Change importance to Low.
Changes for 2023/24:
Change Rural threshold to 20m in line with the Urban metric, to allow for legitimate short lengths such as seal backs , bridge approaches and sections in roundabouts.
Changes for 2024/25:
This metric is changing to Information Only.
CWAY6b - Urban carriageways are generally not short
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Information Only | |
Grade thresholds |
7090
|
The proportion of the number of Urban sealed carriageway records with a length greater than 20m (i.e. not short).
Metric Purpose
Confirm that the sectioning of urban carriageway lengths is appropriate.
Consequence of Poor Quality Data
Short carriageway sections can be difficult, and time consuming to manage and maintain.
Short carriageway sections have the potential to distort the reported results of the ONRC and ONF Amenity Performance Measures.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2020/21:
State Highway urban lengths are short if < 50m.
Changes for 2021/22:
Change importance to Low.
Changes for 2024/25:
Change metric to Information Only.
CWAY7 - Sealed/unsealed network correctly defined
Sub-category | Carriageway | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The percentage of the network length, based on carriageways, with a sealed pavement type and a sealed material surface record, or an unsealed pavement type with either no surface record or an unsealed material surface record.
Metric Purpose
Confirm that the sealed and unsealed networks are correctly defined.
Consequence of Poor Quality Data
Incorrectly defined sealed and unsealed networks can impact setting levels of service, network analysis, renewal and maintenance programme development, condition surveys and achievement and other types of reporting.
Incorrect reporting of ONRC and ONF Cost Efficiency Performance Measures as a result of incorrect sealed network length.
Potential reason(s) for not being at the expected standard unique to this metric
Poor network definition through carriageway sectioning. Poor management of carriageway sections following seal extension works. Incorrect recording of sealed surface inventory data.
Specific comments on the metric
This metric allows for two scenarios for the unsealed network. Either there is no record in the carriageway surface table, or there is a record with a material type of "METAL", or "OTTA".
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2022/23:
Exclude OTTA seals.
Changes for 2023/24:
Remove the check on surface width > 3m.
Changes for 2024/25:
Remove the pairing with CWAY1 as CWAY1 is becoming an Information Only metric.
Add AMDS SQL.
CWAY8 - ONF categories are assigned
Sub-category | Carriageway | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
9598
|
The proportion of the network with an assigned ONF category, by comparing the total ONF length to the total network length.
Metric Purpose
Confirm that an ONF category is recorded for all locally owned road carriageway sections.
Consequence of Poor Quality Data
Parts of road network with no ONF category are potentially excluded, or incorrectly defined, in planning, executing and reporting of maintenance and renewal activity.
Incorrect reporting of ONF Performance Measures results as parts of network will not be included.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process or resources for the ongoing maintenance of this dataset. Lack of clarity or understanding that RCAs are expected to maintain their ONF.
Specific comments on the metric
This metric calculation allows for length adjustments to the carriageways in the network.
This metric only interrogates roads with a Local road type. Paths, walkways, and other parts of the network with a different road type are currently excluded.
This metric excludes duplicate ONF lengths but does not exclude overlapping ONF lengths. Overlapping lengths will skew the results for this metric.
2021/22 Changes
Metric added to Library.
TREAT1 - Treatment Length dimensions match sealed area
Sub-category | Treatment Length | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
8595
|
The percentage of the total number of sealed treatment length records where the recorded sealed area is less than 150% of the calculated area of the treatment length (length * width).
Paired with: TREAT3
Metric Purpose
Confirm consistency between the treatment length dimensions and the sealed area recorded in the surfacing table.
Consequence of Poor Quality Data
When treatment lengths do not match recorded sealed areas, this can result in incorrect dimensions being used for renewal budget forecasting, annual achievement reporting and network statistics.
Incorrectly recorded sealed areas will also affect the results of the ONF and ONRC Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Incorrect surface area recorded in carriageway surface table record. Short treatment lengths which include 'extra areas' e.g. intersections, side road thresholds, etc. Incorrectly recorded carriageway widths in carriageway table.
Specific comments on the metric
150% has been selected as this is an existing value used within the AWM "Status Check" processes when summarising data into the treatment length table.
The metric excludes short treatment lengths (<50m in length) from the "less than 150%" value.
Changes for 2021-22
Exclude short treatment lengths <50m in length.
Pair with metric TREAT3.
TREAT2a - Treatment Lengths are generally not short
Sub-category | Treatment Length | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Low | |
Grade thresholds |
7590
|
The proportion of the number of sealed treatment length records that are not very short (i.e., <20m). Disabled treatment lengths, short sealed back sections, and bridges are all excluded from the calculation.
Paired with: TREAT2b
Metric Purpose
Confirm that treatment length sectioning length is appropriate.
Consequence of Poor Quality Data
Short lengths can be difficult/impractical to manage and maintain.
Very short treatment lengths have the potential to impact the results of the ONRC Amenity Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process, understanding or resources for the ongoing maintenance of this dataset.
Lack of understanding on how to manage treatment length sectioning within the asset management system.
Lack of understanding of the consequence of having a large number of short sections.
Specific comments on the metric
The limits have been set around practical lengths for managing and maintaining the pavement and surfacing assets, while allowing for intersections and cul-de-sac heads, etc.
It is expected that some treatment lengths will be legitimately short. The grade ranges were chosen by the project team to allow for these exceptions.
Changes for 2021/22
Change importance to Low. Exclude short sealed back sections from the total count and exceptions.
Changes for 2024/25
Check for 20m sections for both Urban and Rural.
TREAT2b - Treatment Lengths are not too long
Sub-category | Treatment Length | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Low | |
Grade thresholds |
7590
|
The proportion of the number of sealed treatment length records that are not exceptionally long. Exceptionally long is considered to be:
- >1km Urban
- >2km Rural
Metric Purpose
Confirm that treatment length sectioning length is appropriate.
Consequence of Poor Quality Data
Long lengths can be difficult/impractical to manage and maintain. The uniformity of condition and performance are likely to be more varied over a greater section.
Very long treatment lengths have the potential to impact the results of the ONRC and ONF Amenity Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process, understanding or resources for the ongoing maintenance of this dataset.
Lack of understanding on how to manage treatment length sectioning within the asset management system.
Lack of understanding of the consequence of having a large number of long sections.
Specific comments on the metric
The limit has been set around practical lengths for managing and maintaining the pavement and surfacing assets. The grade ranges were chosen by the project team to allow for potential exceptions.
Changes for 2021/22
Change metric to Low importance.
Changes for 2024/25
Change the limits to 1km for Urban and 2km for Rural.
TREAT3 - Treatment Lengths match major surfaces
Sub-category | Treatment Length | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
7090
|
The proportion of the number of treatment length records where the major top surface length covers at least 80% of the treatment length.
Paired with: TREAT1
Metric Purpose
Confirm that treatment length sectioning aligns with major top surface records.
Consequence of Poor Quality Data
Misalignment indicates the potential that sectioning does not reflect how pavement and surfacing assets are being managed and maintained.
Network level decision-making can also be misinformed through summarising of asset inventory and condition data to inappropriate sectioning.
Misalignment can also impact the results of the ONF and ONRC Amenity Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of process, understanding or resources for the ongoing maintenance of this dataset.
Lack of understanding on how to manage treatment length sectioning within the asset management system.
Specific comments on the metric
The 80% coverage has been selected as this is an existing extent already reported in RAMM.
Changes for 2024/25
Set the metric to High importance to match TREAT1. Check surface length coverage rather than area coverage to allow for RCAs carrying out more lane treatments due to cost.
TREAT5 - Treatment Lengths match renewals
Sub-category | Treatment Length | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The proportion of the number of treatment length records where the major top surface length covers at least 80% of the treatment length where the surface date is in the reported financial year.
Metric Purpose
Confirm that treatment length sectioning is being maintained and updated following renewal activity.
Consequence of Poor Quality Data
Network level decision-making can be misinformed through summarising of asset inventory and condition data to inappropriate sectioning.
Misalignment can also impact the results of the ONF and ONRC Amenity Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Poor processes, or lack of resources for the management and maintaining of treatment length sectioning in a timely manner.
Specific comments on the metric
The 80% coverage has been selected as this is an existing extent already reported in RAMM.
Changes for 2021/22
No longer use #tempDate.
Changes for 2022/23
Report as NA if no treatment lengths updated in the year.
Changes for 2024/25
Compare surface length rather than area to allow for RCAs carrying out more lane treatments rather than full width treatments due to cost.
PAVE1 - Achieved pavement renewal programme as-builted
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
8595
105
115
|
The percentage of the achieved pavement renewals reported in TIO as-builted in RAMM with a work category of 214 for last financial year.
Metric Purpose
Confirm the financial years pavement renewals achievement reported in TIO have been recorded, and are identifiable in RAMM.
Consequence of Poor Quality Data
Poor capture of pavement renewals in RAMM can have an impact on modelling outputs and forward works programming including analysis, annual achievement reporting and investment decision making.
Poor data will impact the results of the ONF and ONRC Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of, or poor process for recording correct work category in the pavement layer table for pavement renewal work claimed under work category 214. Reported achieved quantity from different source than as-builted records in RAMM. Source data used for reporting achievements is not complete or up to date when needed.
Specific comments on the metric
The metric compares RAMM totals to what is recorded in TIO. An exact match will give a metric result of 100%.
The threshold for minor issues is more than +/- 5% of an exact match i.e. RAMM is less than 95% of TIO or more than 105%.
The threshold for major issues is more than +/- 15% of an exact match i.e. RAMM is less than 85% of TIO or more than 115%.
Changes for 2019/20
Metric has been updated to report where road_type = 'L' and owner_type = 'L' only.
Changes for 2021/22
Move to Asset Inventory subcategrory Pavement & Surfacing. Report using Work Category from carriageway surface rather than from pave structure. No longer use #tempDate.
Changes for 2023/24
Add the AMDS RAMM SQL for the metric using the AMDS surface tables.
Do not restrict to major surfaces.
Changes for 2024/25
Change PAVE1 to use sealed area (total area for AMDS).
PAVE2 - Pavement layer records have valid attribute data
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
9598
|
The percentage of pavement layer records with a layer date in the reported financial year and a known material and source, recorded width when not full width, recorded thickness between 20mm and 500mm, and recorded Work Origin.
Metric Purpose
Confirm pavement records attribute data added in the reported financial year is likely to be accurate and thus is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Without populated attribute data for pavement records, analysis and investment decision-making could be impacted due to data exclusions or assumptions for missing information.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM. The system allows for invalid records to be entered. Lack of data standard on how geotextile/fabric layers are to be recorded.
Changes for 2019/20
Metric has been updated to exclude pavement layers with a material type of 'SEALS'.
Also 'UNKNOWN' has been added to the variations used to record an unknown pavement material source.
Changes for 2021/22
Move to Asset Inventory subcategory Pavement & Surfacing. Use pave structure instead of pave layer. No longer use #tempDate.
Changes for 2022/23
Report as N/A if no pavement layer records added in the reported financial year.
Changes for 2023/24
Only include Major structures.
Add AMDS RAMM SQL.
Changes for 2024/25
Merge PAVE3 into PAVE2: test work origin in PAVE2. Apply the AMDS minimum of 20mm.
SURF1a - Achieved chipseal resurfacing renewal programme as-builted
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
8595
105
115
|
The percentage of the achieved chipseal resurfacing renewals reported in TIO as-builted in RAMM (in m2) with a work category of 212 for reported financial year.
Paired with: SURF1b
Metric Purpose
Confirm the financial years chipseal renewals achievement reported in TIO have been recorded, and are identifiable in RAMM.
If reseals that have short lengths or narrow widths are not loaded into RAMM, this could effect the result of this metric.
Consequence of Poor Quality Data
Poor capture of chipseal resurfacing renewals in RAMM can have an impact on modelling outputs and forward works programming including analysis, annual achievement reporting and investment decision making.
Poor data will impact the results of the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of, or poor process and trained personnel for recording correct work category in the carriageway surface table for sealed resurfacing work claimed under work category 212.
Reported achieved quantity from different source than as-builted records in RAMM.
Source data used for reporting achievement is not complete or up to date when needed.
Uncertainty around the work category to assign the surfacing component of the pavement rehabilitation to.
Specific comments on the metric
The metric compares RAMM totals to what is recorded in TIO. An exact match will give a metric result of 100%.
The threshold for minor issues is more than +/- 5% of an exact match i.e. RAMM is less than 95% of TIO or more than 105%.
The threshold for major issues is more than +/- 15% of an exact match i.e. RAMM is less than 85% of TIO or more than 115%.
Changes for 2019/20:
Metric has been updated to report where road_type = 'L' and owner_type = 'L' only.
Changes for 2021/22:
Move to Asset Inventory subcategory Pavement & Surfacing. Use Work Category on c_surface. No longer use #tempDate.
Changes for 2022/23:
Report on the surface structure sealed area first if it is populated, else use width * length.
Changes for 2023/24:
Add AMDS RAMM SQL for the metric.
Do not restrict to only major surfaces.
SURF1b - Achieved asphaltic concrete resurfacing renewal programme as-builted
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
8595
105
115
|
The percentage of the achieved asphaltic concrete resurfacing renewals reported in TIO as-builted in RAMM (in m2) with a work category of 212 for reported financial year.
Paired with: SURF1a
Metric Purpose
Confirm the financial years asphalt renewals achievement reported in TIO have been recorded, and are identifiable in RAMM.
If reseals that have short lengths or narrow widths are not loaded into RAMM, this could effect the result of this metric.
Consequence of Poor Quality Data
Poor capture of asphaltic concrete resurfacing renewals in RAMM can have an impact on modelling outputs and forward works programming including analysis, annual achievement reporting and investment decision making.
Poor data will impact the results of the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of, or poor process and trained personnel for recording correct work category in the carriageway surface table for sealed resurfacing work claimed under work category 212.
Reported achieved quantity from different source than as-builted records in RAMM.
Source data used for reporting achievement is not complete or up to date when needed.
Uncertainty around the work category to assign the surfacing component of the pavement rehabilitation to.
Specific comments on the metric
The metric compares RAMM totals to what is recorded in TIO. An exact match will give a metric result of 100%.
The threshold for minor issues is more than +/- 5% of an exact match i.e. RAMM is less than 95% of TIO or more than 105%.
The threshold for major issues is more than +/- 15% of an exact match i.e. RAMM is less than 85% of TIO or more than 115%.
Changes for 2019/20
Metric has been updated to report where road_type = 'L' and owner_type = 'L' only.
Changes for 2021/22
Move to Asset Inventory subcategory Pavement & Surfacing. No longer use #tempDate. Update the RAMM SQL to use c_surface.
Changes for 2022/23
Report on m2 rather than lane km, to be consistent with SURF1a and PAVE1. Report on sealed area if populated otherwise length * width.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Include Slurry Seal even if it does not have an AM category. Do not restrict to just major surfaces.
SURF2 - Surface records have valid attribute data
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
9598
|
The percentage of current top surface records, based on the surface structure, with a valid chip size (AM>=7, CS<=6, 2nd chip recorded for 2CHIP, RACK, B/S, 3CHIP, CAPE, and COMB), surface function (AC <> "M"), a recorded binder type, and a recorded top surface life.
Paired with: SURF3
Metric Purpose
Confirm surface records attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Without populated attribute data, surface records could have no network-level expected surface life, which could impact life cycle analysis and investment decision-making.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM. The system allows for invalid records to be entered.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, there are surface records that will legitimately fail this validation test (i.e. Slurry surfaces). These typically constitute a small proportion of each network and have been considered in setting the grade ranges for this metric.
For AMDS, AWM currently populates a default chip size of 1 to the treatment length for AC rather than recording the mix designation number as the chip size, so the AC "chip size" test is not possible for AMDS using treatment length data alone. The metric joins to the surface structure table for that check.
Changes for 2020/21
Include COMB in the surface material list.
Changes for 2021/22
Pair this metric with SURF3. 1st Coat is a valid surface function for AC.
Changes for 2023/24
Add AMDS SQL. Allow for AMDS not bringing through the first coat size for AC to the treatment lengths.
Changes for 2024/25
For AMDS databases, AWM currently populates a default chip size of 1 to the treatment length for AC rather than recording the mix designation number as the chip size, so the AC "chip size" test is not possible for AMDS when using treatment length data alone. The metric uses surface structure for that check.
SURF3 - Surface records correctly located
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The proportion of the number of surface records entered to RAMM with a surface date in the reported financial year that have a recorded start and end displacement within the limits of the road as defined in the carriageway table, and have a recorded surface width no greater than 2m wider than the carriageway width.
Paired with: SURF2
Metric Purpose
Confirm that the recorded surface inventory records in the financial year align with the network as defined in the carriageway table.
Consequence of Poor Quality Data
Potentially inaccurate data could be used to support decision-making processes, and the data summarised into the treatment length table will not reflect the network dimensions.
This could also result in incorrect reporting of renewal quantity and achieved life which feed into the ONRC AND ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Poor QA process around as-built data collection.
Carriageway sectioning not actively managed/maintained.
Terratrip used for measuring start and end displacements not calibrated.
Specific comments on the metric
Not greater than 2m wider than the carriageway width was selected based on the guidance in SHDOM that a change in width of >2m should become a new carriageway section.
Changes for 2021/22
Pair this metric with SURF2. No longer use #tempDate.
Changes for 2023/24
Add AMDS RAMM SQL for this metric.
Allow for a mix of locally owned and private/crown sections along a road.
SURF4 - Surface records with Original Cost and Work Category
Sub-category | Pavement & Surfacing | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The proportion of surface records entered into RAMM with a surface date in the financial year and a Work Category assigned, and an original cost recorded where the recorded Work Category is 212 or 214.
Metric Purpose
Confirm surface records attribute data added in the reported financial year is likely to be accurate and thus is adequate for planning and decision-making purposes
Consequence of Poor Quality Data
Without a recorded original cost and work origin, there will be a reduced understanding of investment and performance, along with incorrect reporting of renewal quantity and achieved life which feed into the ONF and ONRC Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Poor or lack of process for the population of this attribute field. Lack of understanding of what costs are to be recorded.
Specific comments on the metric
30 June 2016 was selected as population of the original cost and work origin fields were requested of the sector from the 2016/17 financial year onwards.
Changes for 2020/21
The metric will report for the previous financial year only.
Changes for 2021/22
Pair this metric with SURF5.
Changes for 2022/23
Report as NA if no surfaces have been updated in the year.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
SURF5 is merged into SURF4.
SURF6 - Surface records newer than pavement
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Moderate | |
Grade thresholds |
8095
|
The percentage of the length, based on treatment lengths, where the major top surface is newer than the underlying major pavement layer, the recorded pavement layer date is less than 3.5 years old at the end of the reported financial year, and the major pavement layer coverage is >=50% of the treatment length.
Metric Purpose
Confirm that a surface record exists for all pavement layer records added to the database in the last 3.5 years.
Consequence of Poor Quality Data
Where there is a newer pavement date than the surface date, this indicates a data error which could impact future renewal need analysis, forecasting and programming.
This could also mean incorrect reporting of renewal quantity and achieved life which feed into the ONF and ONRC Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
No pavement layer data covering the majority of the treatment length section (i.e. major pavement layer and major surface records are for different portions of the treatment length).
Lack of use of pavement builder for completing inventory record updates in RAMM.
Poor, or lack of, process for managing and maintaining pavement and surfacing asset data.
Specific comments on the metric
The grade ranges make an allowance for treatment lengths which have little pavement layer data and the major pavement layer is associated with a shoulder widening, or similar.
The metric only includes treatment lengths where the major pavement layer coverage is >=50% of the treatment length.
Changes for 2021/22
Only include where the major pavement layer coverage is >=50% of the treatment length. No longer use #tempDate.
Changes for 2023/24
Exceptions SQL checks for treatment lengths with missing surface dates.
FOOT2 - Footpath asset records maintained
Sub-category | Pathways | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
13
|
The percentage of the total "in use" footpath (pathway) length entered to RAMM during the three year period to the end of the reported financial year.
Metric Purpose
Confirm that footpath (pathway) asset data is being added as new footpaths (pathways) are constructed/vested, and others are renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Changes for 2019/20
Importance level for metric has been changed to Low.
Changes for 2021/22
Moved to Asset Inventory subcategory Pathways. No longer use #tempDate in the RAMM SQL.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
Change the metric to Information Only.
FOOT3 - Footpath data valid
Sub-category | Pathways | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
9598
|
The percentage of "in use" footpath (pathway) records with a valid recorded length (not null or zero), and width (>0.7m and <20m, and not null), an offset less than 40m (when recorded), surface date >= construction date and condition date (when recorded) >= surface date.
Metric Purpose
Confirm footpath (pathway) assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that footpath (pathway) assets are likely to be assigned to the correct road.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for 'historical' assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, there will be instances where a footpath (pathway) width falls outside the allowed range of this test.
Less than three years old has been considered a recent condition date.
Changes for 2021/22
New metric.
Changes for 2022/23
Add exception SQL.
Changes for 2023/24
Add AMDS RAMM and Exception SQL for the metric.
Changes for 2024/25
For AMDS: Only include In Use assets. Treat the default install date of 1 Jan 1900 as no install date.
FOOT5 - Footpath asset known
Sub-category | Pathways | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
8595
|
The percentage of the total number of "in use" footpath (pathway) records with a known purpose, asset owner, location (start and end displacements and side), surface material and construction/surface date.
Metric Purpose
Confirm completeness of footpath (pathway) assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data may not be known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments about the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, there will be instances where a footpath (pathway) width falls outside the allowed range of this test.
Less than three years old has been considered a recent condition date.
Changes for 2021/22
New metric replacing FOOT1.
Changes for 2022/23
Use the asset owner of the footpath rather than the owner type of the carriageway section.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
For AMDS, only check In Use assets. Extend the corridor boundary checks and increase the grade thresholds to allow for the extended boundary. Add RAMM and AMDS Exception SQL.
DRAIN2 - Culvert asset records maintained
Sub-category | Drainage System | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
13
|
The percentage of the total "in use" culvert (pipe) length entered into RAMM during the three year period to the end of the reported financial year.
Metric Purpose
Confirm that culvert (pipe) asset data is being added as new culverts (pipes) are constructed/vested, and others are renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Changes for 2019/20:
Importance level of metric has been changed to Low.
Changes for 2021/22:
Moved to Asset Inventory subcategory Drainage System.
DRAIN2 and SWC2 are now paired so together they only count as one metric for the score. No longer use #tempDate in the RAMM SQL.
Changes for 2022/23:
Use the asset owner of the drainage record rather than the owner type of the carriageway section.
Changes for 2023/24:
Add AMDS RAMM SQL for DRAIN2.
Changes for 2024/25:
The metric is now for Information Only.
DRAIN3 - Culvert data valid
Sub-category | Drainage System | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
9598
|
The percentage of "in use" culvert (pipe) records with a valid recorded length (not null or zero), and diameter/height (>=100mm and <8,000mm, and not null), an offset less than 40m (when recorded), and condition date (when recorded) >= construction date.
Paired with: SWC3
Metric Purpose
Confirm culvert (pipe) assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that the culvert (pipe) assets are likely to be assigned to the correct road.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for 'historic' assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, unknown constructed dates of 'older' assets and the ease and value of estimating these has been considered.
Less than three years old has been considered a recent condition date.
The metric will treat a construction/installation date of 1 Jan 1900 as an unknown date. 1 Jan 1900 is a default loading date in AMDS when there is no construct date, as the install date in AMDS is a required field.
Changes for 2021/22
Metric created.
Changes for 2024/25
Treat a construction/installation date of 1 Jan 1900 as an unknown date. 1 Jan 1900 is a default loading date in AMDS when there is no construct date, as the install date in AMDS is a required field.
DRAIN5 - Culvert assets known
Sub-category | Drainage System | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
6080
|
The percentage of the number of "in use" culvert (pipe) records with a known drainage type, asset owner, location (displacement and side), material, culvert type (i.e. not "unknown") and construction date.
Paired with: SWC5
Metric Purpose
Confirm completeness of culvert (pipe) assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for 'historic' assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for unknown constructed dates of 'older' assets and the ease and value of estimating these.
northing and easting definitions are not in the AMDS schemas so these attributes are no longer tested in the Data Quality metrics.
The metric no longer tests for culverts positioned beyond the end of the road.
Only include In Use assets for RCAs on AMDS.
Changes for 2021/22
New metric replacing DRAIN1.
Changes for 2022/23
Allow for assets located at the very end of the road. Use the asset owner of the drainage record rather than the owner type of the carriageway section.
Changes for 2023/24
Add the AMDS RAMM SQL for DRAIN5.
Changes for 2024/25
The metric no longer tests for culverts positioned beyond the end of the road. Also, northing and easting definitions are not in the AMDS schemas so these attributes are no longer tested in the Data Quality metrics.
Only include In Use assets for RCAs on AMDS.
SWC2 - SWC asset records maintained
Sub-category | Drainage System | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
13
|
The percentage of the total "in use" surface water channel (channel) length entered to RAMM during the three year period to the end of the reported financial year.
Metric Purpose
Confirm that surface water channel (channel) asset data is being added as new surface water channels (channels) are constructed/vested, and others are renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Changes for 2019/20
Importance level changed to Low.
Changes for 2020/21
The metric will exclude ESWC type.
Changes for 2021/22
Moved to Asset Inventory subcategory Drainage System. No longer use #tempDate in the RAMM SQL.
DRAIN2 and SWC2 are now paired so together they only count as one metric for the score.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
Change the metric to Information Only.
SWC3 - SWC data valid
Sub-category | Drainage System | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
9598
|
The percentage of "in use" surface water channel (channel) records with a valid recorded length (not null or zero), an offset less than 40m (when recorded) and condition date (when recorded) >= construction date.
Paired with: DRAIN3
Metric Purpose
Confirm surface water channel (channel) assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that the surface water channel (channel) assets are likely to be assigned to the correct road.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for 'historic' assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
Excludes surface water channel types of:
- SWCD (Surface Water Channel (Deep, >200 Below Seal Edge)),
- SWCS (Surface Water Channel (Shallow, <200 Below Seal Edge)),
- ESWC (Earth Surface Water Channel).
Changes for 2020/21
The metric will exclude the ESWC type.
Changes for 2022/23
Refer to the assets as surface water channels rather than kerb and channel.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
only include In Use assets for AMDS.
SWC5 - SWC asset known
Sub-category | Drainage System | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
8090
|
The percentage of the number of "in use" surface water channel (channel) records with a known channel type, asset owner, location (start and end displacement and side) and construction date.
Paired with: DRAIN5
Metric Purpose
Confirm completeness of surface water channel (channel) assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for 'historic' assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
Excludes surface water channel types of:
- SWCD (Surface Water Channel (Deep, >200 Below Seal Edge)),
- SWCS (Surface Water Channel (Shallow, <200 Below Seal Edge)),
- ESWC (Earth Surface Water Channel).
Changes for 2021/22
New metric replacing SWC1.
Changes for 2022/23
Clarify reference to surface water channels rather than kerb and channel.
Use the asset owner of the surface water channel record rather than the owner type of the carriageway section.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
Remove northing/easting check and extend boundary check. Only include In Use assets.
LIGHTS3 - Streetlight replacement activity
Sub-category | Traffic Facilities & Streetlights | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
36
|
The percentage of the total number of "in use" streetlight lights (luminaires) recorded as replaced in RAMM for the three year period to the end of the reported financial year. Excludes when only lamp and/or gear is replaced.
Metric Purpose
Confirm that streetlight (luminaire) asset data is being maintained as streetlight lights (luminaires) are replaced/renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Specific comments on the metric
For RCAs that have migrated to AMDS, the metric will filter using the owner of the luminaire. Where a luminaire also has a sub organisation assigned, the luminaire will be included if the owner type of the sub organisation is 'LA'. The metric will also check luminaires that are not attached to poles.
For RCAs that have not yet migrated to AMDS, the metric will continue to use the owner of the carriageway section that the pole is located on, as the owner of the light cannot be accurately identified. Classic RAMM also still requires that a light be attached to a pole.
LIGHTS3 is now an Information Only metric.
Changes for 2019/20
Metric changed from reporting the percentage of streetlight pole to streetlight light records with a replacement date in the last three financial years.
Excludes when lamp and/or gear only have been replaced.
Grade ranges also updated to reflect different expected lives.
Changes for 2022/23
The logic now ensures lights are not double counted due to the lighting configuration.
Changes for 2023/24
Add the AMDS RAMM SQL for the metric.
For RCAs that have migrated to AMDS, the metric will filter using the owner of the light. For RCAs that have not yet migrated to AMDS, the metric will continue to use the owner of the carriageway section that the pole is located on.
Changes for 2024/25
For RCAs that have migrated to AMDS, the metric will check luminaires that are not attached to outreaches or poles, and will only check In Use and replaced assets.
LIGHTS3 is now an Information Only metric.
LIGHTS4 - Streetlights data valid
Sub-category | Traffic Facilities & Streetlights | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
9598
|
The percentage of the number of "in use" streetlight (luminaire) records located within the extents of the road as defined in the carriageway table and with an offset less than 40m (when recorded), and with condition date >= installation date (when recorded).
Paired with: RAIL3, SIGNS5
Metric Purpose
Confirm that streetlight (luminaire) assets are likely to be correctly located in relation to how the network is defined by the carriageway table, and that condition data is not out of date.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM. Displacements recorded using an uncalibrated trip meter.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, if streetlight (luminaire) assets have been added into the database before the newly constructed road that they should sit on, they may have an offset that falls outside the defined ranges as they are temporarily assigned to another road.
For RCAs that have migrated to AMDS, the metric will filter using the owner of the light (luminaire) as AMDS allows for lights (luminaires) to exist with no outreach or pole. Where a light (luminaire) also has a sub organisation assigned, the light (luminaire) will be included if the owner type of the sub organisation is 'LA'.
For RCAs that have not yet migrated to AMDS, the metric will continue to use the owner of the carriageway section that the pole is located on, as the owner of the light (luminaire) cannot be accurately identified.
The metric only reports on In Use assets for AMDS.
Changes for 2021/22
Also check condition date is on or after install date if condition date is entered. Allow for a blank offset.
Changes for 2023/24
Add the AMDS RAMM and Exception SQL for the metric.
Pair the LIGHTS4 metric with RAIL3 and SIGNS5.
Changes for 2024/25
Change the metric to count lights rather than poles as under AMDS the luminaire may not have an outreach nor a pole.
Remove the northing/easting check as this is not available in AMDS and extend the location boundary checking to allow for lights past the end of the road eg cul-de-sacs.
Only include In Use assets for AMDS.
LIGHTS5 - Streetlight assets known
Sub-category | Traffic Facilities & Streetlights | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
6080
|
The percentage of the number of "in use" streetlight light (luminaire) records with a known pole and light owner, known pole make and mounting type, known light make and model, known lamp make and model and pole and light installation dates. (Pole make, light make and light model cannot be checked for AMDS RCAs.)
Paired with: RAIL4, SIGNS4
Metric Purpose
Confirm completeness of streetlight light (luminaire) assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM.
Comments specific to the metric
AMDS supports luminaires not being attached to an outreach (bracket) or pole. Luminaires will be checked by this metric even if not attached to an outreach or pole.
Also, pole make, light make and light model are not in the AMDS standard so will not be checked for RCAs that have migrated to AMDS.
Changes for 2021/22
New metric replacing LIGHTS2.
Changes for 2023/24
Count the number of lights instead of the number of poles. Update the description in the RAMM SQL. Add the AMDS RAMM SQL for the metric.
Changes for 2024/25
Only include In Use assets. Check AMDS luminaires not attached to an outreach or pole. Check for the default install date of 1 Jan 1900.
RAIL2 - Railing asset records maintained
Sub-category | Traffic Facilities & Streetlights | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
36
|
The percentage of the total "in use" railing (barrier) length entered in RAMM for the three year period to the end of the reported financial year.
Metric Purpose
Confirm that railing (barrier) asset data is being added as new railings (barriers) are installed/vested, and others are renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for updating the asset inventory table following renewal activity Renewal activity is delivered in quantities less than that identified for capitalisation by internal processes.
Specific comments on the metric
For AMDS, this metric will check the barriers table.
Changes for 2021/22
Pair this metric with SIGNS3 and LIGHTS3.
Changes for 2023/24
Add AMDS RAMM SQL for this metric.
Changes for 2024/25
Change the metric to Information Only.
RAIL3 - Railing data valid
Sub-category | Traffic Facilities & Streetlights | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
9598
|
The percentage of "in use" railing (barrier) records with a valid recorded length (not null or zero), an offset less than 40m (when recorded) and condition date (when recorded) >= installation date.
Paired with: LIGHTS4, SIGNS5
Metric Purpose
Confirm railing (barrier) assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that railing (barrier) assets are likely to be assigned to the correct road.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, unknown constructed dates of 'older' assets and the ease and value of estimating these has been considered.
Less than three years old has been considered a recent condition date.
For AMDS, this metric will check the barriers table.
Changes for 2021/22
Metric created.
Changes for 2023/24
Add AMDS SQL for the metric.
Pair the RAIL3 metric with LIGHTS4 and SIGNS5.
Changes for 2024/25
Only include In Use assets.
RAIL4 - Railing assets known
Sub-category | Traffic Facilities & Streetlights | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
6080
|
The percentage of the number of "in use" railing (barrier) records with a known railing type, asset owner, location (start and end displacement and side), material and installation date.
Paired with: LIGHTS5, SIGNS4
Metric Purpose
Confirm completeness of railing (barrier) assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for unknown constructed dates of older assets and the ease and value of estimating these.
For AMDS, this metric will check the barriers table.
Changes for 2021/22
New metric replacing RAIL1.
Changes for 2022/23
Use the asset owner of the railing record rather than the owner type of the carriageway section.
Changes for 2023/24
Add the AMDS RAMM SQL for the metric.
Changes for 2024/25
Remove the northing/easting check and extend the road boundary check. Only include In Use assets for AMDS.
SIGNS3 - Sign replacement activity
Sub-category | Traffic Facilities & Streetlights | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
710
|
The percentage of the total number of "in use" signs recorded as replaced in RAMM for the three year period to the end of the reported financial year.
Metric Purpose
Confirm that sign asset data is being maintained as signs are replaced/renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Changes for 2021/22
Pair with RAIL2 and LIGHTS3. No longer use #tempDate in the RAMM SQL.
Changes for 2024/25
Change the metric to Information Only.
SIGNS4 - Sign assets known
Sub-category | Traffic Facilities & Streetlights | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
6080
|
The percentage of the number of "in use" sign records with recorded owner, class, type, material (background and legend), colour (background and legend), and installation date or recent known condition.
Paired with: LIGHTS5, RAIL4
Metric Purpose
Confirm completeness of sign assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact investment decisions and asset valuations, and also could result in a lack of maintenance response.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions.
Less than 3 years old has been considered a recent condition date.
For RCAs that have migrated to AMDS, the metric will check sign type and class for Traffic Control Device (TCD) signs and will just check type for non-TCD signs. Also none of legend material, legend colour, and background material are in AMDS.
Changes for 2020/21
Exclude condition clause for State Highways.
Changes for 2021/22
New metric replacing SIGNS1.
Changes for 2023/24
For RCAs that have migrated to AMDS, the metric will check sign type and class for Traffic Control Device (TCD) signs and will just check type for non-TCD signs.
Changes for 2024/25
Only include In Use assets for AMDS.
SIGNS5 - Sign data valid
Sub-category | Traffic Facilities & Streetlights | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
9598
|
The percentage of the number of "in use" sign records located within the extents of the road and with a location and an offset less than 40m (when recorded), a height >=50mm and <=5000mm (when recorded), a width >=100mm and <=5000mm (when recorded), and condition date >= installation date (when recorded).
Paired with: LIGHTS4, RAIL3
Metric Purpose
Confirm sign assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that sign assets are correctly located in relation to how the network is defined by the carriageway table.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact investment decisions and result in a lack of maintenance response.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM. Displacements recorded using an uncalibrated trip meter.
Specific comments on the metric
The sign height limit is set to 50mm to allow for shorter height signs such as No Exit signs.
Changes for 2021/22
New metric replacing SIGNS2.
Changes for 2022/23
Update the width and height checks to be >=100mm and <=5000mm. This allows for Rural Address Property Identification signs that are 100mm high.
Changes for 2023/24
Add the AMDS RAMM and Exception SQL for the metric.
Pair the SIGNS5 metric with LIGHTS4 and RAIL3.
Adjust the sign height limit from 100mm to 50mm, to allow for shorter height signs such as No Exit signs.
Changes for 2024/25
Only include In Use assets. Remove northing/easting check and extend road boundary check. Align with AMDS minimum dimensions.
RETAIN2 - Retaining wall asset records maintained
Sub-category | Structures | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
12
|
The percentage of the total "in use" retaining wall length entered in RAMM during the five year period to the end of the reported financial year.
Metric Purpose
Confirm that retaining wall asset data is being added as new retaining walls are constructed/vested, and others are renewed.
Consequence of Poor Quality Data
Poor updating of data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor updating of data can also result in inaccurate asset counts in asset valuations.
Changes for 2019/20
Metric has been changed to report a result of "NA" for RCAs with no retaining walls recorded in their database. This is then ungraded and excluded from the aggregated results.
Changes for 2021/22
Move to Asset Inventory subcategory Structures. Just look up assets using asset_owner.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Changes for 2024/25
Changed the metric to Information Only.
RETAIN3 - Retaining wall data valid
Sub-category | Structures | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
9598
|
The percentage of "in use" retaining wall records with a valid recorded length (not null or zero), average height >=0.3m and <40m, an offset less than 40m (when recorded) and condition date (when recorded) >= construction date.
Metric Purpose
Confirm retaining wall assets attribute data is likely to be accurate and thus is adequate for planning and decision-making purposes. Confirm that the retaining wall assets are likely to be assigned to the correct road.
Consequence of Poor Quality Data
Inaccurate data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Incorrect road assignment also could lead to confusion and inefficiencies with inspections and other site based work.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions. For example, unknown constructed dates of 'older' assets and the ease and value of estimating these has been considered.
The height limit is set to 40m to try to catch cases where the height has been entered incorrectly eg 4.5 has been entered as 45.
Changes for 2021/22
Metric created.
Changes for 2022/23
Move checks on wall type and material to new metric RETAIN5.
Changes for 2023/24
Add AMDS SQL for RETAIN3. Only report on installed walls for AMDS as AMDS allows for other statuses as well.
Increase height limit from 8m to 10m to allow for higher walls but still catch incorrectly entered heights eg. 1.5 entered as 15.
Changes for 2024/25
Increase height limit further to 40m as there is a reasonable number of higher retaining walls in RCAs. Only include In Use assets for AMDS.
RETAIN5 - Retaining Wall assets known
Sub-category | Structures | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
6080
|
The percentage of the number of retaining wall records with a known type, asset owner, location (start and end displacement and side), material, and construction date.
Metric Purpose
Confirm completeness of retaining wall assets attribute data is adequate for planning and decision-making purposes.
Consequence of Poor Quality Data
Poor data has the potential to result in misinformed decision-making which can impact renewal programme development, financial decisions, asset valuations and LoS delivery.
Potential reason(s) for not being at the expected standard unique to this metric
Attribute data not known for historical assets. Poor, or lack of, clarity on what attribute fields are to be collected and maintained for this asset type. Poor, or lack of quality control undertaken on inventory data.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for unknown constructed dates of older assets and the ease and value of estimating these.
Changes for 2021/22
New metric replacing RETAIN1.
Changes for 2022/23
Only report on locally owned retaining walls. Use the asset owner of the retaining wall record rather than the owner type of the carriageway section.
Changes for 2023/24
Add AMDS SQL for the metric.
Changes for 2024/25
Remove the northing/easting checks and extend the road boundary check. Only include In Use assets for AMDS.
MAINT1 - Consistency of pavement, surfacing and shoulder maintenance activity units
Sub-category | Maintenance Activity | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
21.2
|
The average number of different units used (e.g. each, m, m2, hr, etc.) per fault type (e.g. flushing, high shoulder, pot-hole, etc.) during the reported financial year for pavement (PA), surfacing (SU) and shoulder (SH) cost group maintenance activities. For records with a transaction date within the reported financial year.
Metric Purpose
Confirm the usability of the maintenance activity data to support our decision-making processes.
Consequence of Poor Quality Data
Maintenance data with many different units could result in difficulty using the data in network performance analysis, dTIMS modelling and NPV analysis as it is harder to aggregate and compare.
Potential reason(s) for not being at the expected standard unique to this metric
No defined process for how maintenance activity will be recorded in the maintenance cost table. Poorly defined scope for the set up of RAMM Contractor for the transfer of maintenance activity to the maintenance cost table. Lack of understanding of the intended use of the data in the maintenance cost table. Untrained staff transferring/loading data into the maintenance cost table.
Specific comments on the metric
Metric result is the average number of units per activity. This is not weighted by the number of records within each activity.
Changes for 2019/20:
Metric has been updated to report the number of different units per fault type rather than activity.
Changes for 2021/22:
No longer use #tempDate in the RAMM SQL.
Changes for 2023/24:
Now using a separate UDT to retrieve maintenance costs.
MAINT2 - Complete pavement and surface maintenance activity
Sub-category | Maintenance Activity | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
911
|
The number of months in the reported financial year with at least one maintenance activity record with a cost group of pavement (PA) or surfacing (SU) on the sealed network. For records with a transaction date within the reported financial year.
Metric Purpose
Confirm that pavement and surface maintenance activity is recorded monthly throughout the reported year.
Consequence of Poor Quality Data
Pavement and surfacing maintenance activity data affect judgement on economics of intended investment (i.e. NPV analysis) and understanding of network performance (Condition vs levels of renewals vs levels of maintenance activity), thus a lack of this maintenance data can lead to misinformed decision-making.
Lack of maintenance activity recording will also result in incorrect reporting of maintenance activity levels in the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Poor process or lack of process for the population of the maintenance cost table in RAMM. Lack of available resource for the maintenance of these dataset. Lack of understanding of the value of this dataset.
Specific comments on the metric
The project team have assumed that each month should have at least 1 pavement or surfacing cost group record. The grade ranges make an allowance for this not being the case in one month of the year. The metric does not provide a direct indication of likely accuracy, completeness or timeliness of the maintenance activity data, but it does provide some indication of the effort being applied to capture meaningful data.
Changes for 2021/22:
Change the dimension to Timeliness. No longer use #tempDate in the RAMM SQL.
Changes for 2023/24:
Now using a separate UDT to retrieve maintenance costs.
MAINT3 - Pavement, surfacing, shoulder and drainage maintenance activity known
Sub-category | Maintenance Activity | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
9095
|
The percentage of the number of pavement (PA), surfacing (SU), shoulder (SH) and drainage (DR) cost group maintenance activity records with a known fault type (ie not "unknown"). For records with a transaction date within the reported financial year.
Metric Purpose
Confirm that the reason for the maintenance activity can be understood.
Consequence of Poor Quality Data
Without knowledge of the reason for maintenance activity, there could be an inability to fully understand network performance and investment needs.
Potential reason(s) for not being at the expected standard unique to this metric
Untrained staff collecting as-built inventory data. Lack of data validation checks as part of adding inventory record to RAMM.
Changes for 2021/22:
No longer use #tempDate in the RAMM SQL.
Changes for 2022/23:
Report as No Data if no maintenance activity records are recorded for the reported financial year.
Changes for 2023/24:
Now using a separate UDT to retrieve maintenance costs.
MAINT4 - Correctly located pavement, surface, shoulder and drainage maintenance activity
Sub-category | Maintenance Activity | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
7090
|
The proportion of the number of pavement (PA), surfacing (SU), shoulder (SH) and drainage (DR) cost group maintenance activity records on the sealed network recorded at an appropriate location (i.e., Proportion of records not at the start of the road). For records with a transaction date within the reported financial year.
Metric Purpose
Confirm that the location of pavement and surfacing maintenance activity is recorded and is likely associated with the correct road section.
Consequence of Poor Quality Data
Incorrectly located maintenance activities will impact the outputs of analysis and modelling using this data to consider asset performance and deterioration, e.g. NPV analysis, dTIMS, etc.
Maintenance activity associated with wrong carriageways will also impact how results are reported by ONRC and ONF category for the ONRC and ONF Cost Efficiency Performance Measures.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of, process for the accurate capture of maintenance activity location. Lack of understanding of the value of accurately recording the location of the activity. Cyclic type activities recorded against the start of the road.
Specific comments on the metric
The grade ranges were chosen by the project team to allow for potential exceptions where maintenance activities are legitimately recorded at the start of the road. For example, on a Roundabout, or where a divided carriageway is split with the ascending directions being the direction of travel, resulting in 0m falling in the middle of a road corridor.
Changes for 2020/21
Report MAINT4 for cost groups Surfacing, Pavement, Shoulder and Drainage.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
Changes for 2022/23:
Report as No Data if no maintenance activity records are recorded for the reported financial year.
Changes for 2023/24:
Now using a separate UDT to retrieve maintenance costs.
MAINT6 - Level of pavement, surfacing, shoulder and drainage maintenance activity known
Sub-category | Maintenance Activity | Dimension | Completeness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
9095
|
The percentage of the number of pavement (PA), surfacing (SU), shoulder (SH) and drainage (DR) cost group maintenance activity records with a known quantity (eg not Null, zero or negative). For records with a transaction date within the reported financial year.
Metric Purpose
Confirm that the quantity of maintenance activity has been adequately captured.
Consequence of Poor Quality Data
Without known quantities being recorded, there will be difficulty in using maintenance activity data in network performance analysis, dTIMS modelling and NPV analysis.
Potential reason(s) for not being at the expected standard unique to this metric
No defined process for how maintenance activity will be recorded in the maintenance cost table. Poorly defined scope for the set up of RAMM Contractor for the transfer of maintenance activity to the maintenance cost table.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
Changes for 2022/23:
Report as No Data if no maintenance activity records are recorded for the reported financial year.
Changes for 2023/24:
Report using the new maintenance cost UDT. The adjusted quantity is not required anymore on maintenance cost data in RAMM.
HSD1 - HSD rutting survey within 3 years
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
7090
|
The percentage of the sealed network length, based on carriageway sections, with a latest hsd rutting reading less than 3 years old at the end of the reported financial year.
Metric Purpose
Confirm that the sealed network has recent HSD rutting data. Due to the implementation of CCDC, this metric will no longer count towards the overall Data Quality score.
2021/22 changes
New metric.
2024/25 changes
Change the metric to Information Only with the advent of CCDC.
HSD2 - HSD texture survey within 3 years
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
7090
|
The percentage of the sealed network length, based on carriageway sections, with a latest hsd texture reading less than 3 years old at the end of the reported financial year.
Metric Purpose
Confirm that the sealed network has recent HSD texture data. Due to the implementation of CCDC, this metric will no longer count towards the overall Data Quality score.
2021/22 changes
New metric.
2024/25 changes
Change the metric to Information Only with the advent of CCDC.
HSD3 - HSD geometry survey within 5 years
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
7090
|
The percentage of the sealed network length, based on carriageway sections, with a latest hsd geometry reading less than 5 years old at the end of the reported financial year.
Metric Purpose
Confirm that the sealed network has recent HSD geometry data. Due to the implementation of CCDC, this metric will no longer count towards the overall Data Quality score.
2021/22 changes
New metric.
2024/25 changes
Change the metric to Information Only with the advent of CCDC.
RATING1 - Road rating data current
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
7095
|
The percentage of total sealed network length, based on treatment lengths, with a latest road rating record less than two years old at end of reported financial year.
Metric Purpose
Confirm that the sealed network has recent visual road rating data. Due to the implementation of CCDC, this metric will no longer count towards the overall Data Quality score.
Consequence of Poor Quality Data
A lack of condition data has the potential to affect our ability to identify maintenance and renewal needs, make investment decisions, and measure the effectiveness of investment.
Changes for 2021/22
Move the metric to Condition subcategory Pavement & Surfacing. Change the primary dimension to Timeliness. No longer use #tempDate in the RAMM SQL. Include rating records up to the end of year date.
Changes for 2024/25
Metric changed to Information Only with the advent of CCDC.
RATING2 - Rating data locations valid
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | Information Only |
Grade thresholds |
9598
|
The percentage of the number of latest rating records less than two years old at the end of the reported financial year with a valid inspection section (inspection start >= rating start and start of road, inspection end <= rating end and end of road).
Metric Purpose
Confirm the inspection section locational accuracy against rating sections and the extents of the network as defined by the carriageway table. Due to the implementation of CCDC, this metric will no longer count towards the overall Data Quality score.
Consequence of Poor Quality Data
Any data located outside of the network as defined in the carriageway table is likely to not be included in any analysis or investment decision-making.
Changes for 2021/22
Move the metric to Condition subcategory Pavement & Surfacing. No longer use #tempDate in the RAMM SQL.
Changes for 2024/25
Metric changed to Information Only with the advent of CCDC.
ROUGH1 - Roughness survey within 3 years
Sub-category | Pavement & Surfacing | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | Information Only | |
Grade thresholds |
7090
|
The percentage of the sealed network length, based on carriageway sections, with a latest roughness reading less than three years old at the end of the reported financial year.
Metric Purpose
Confirm that the sealed network has recent roughness data.
Consequence of Poor Quality Data
Out of date data is likely to result in poor reporting of LoS achieved, other key statistics, effectiveness of investment, and network performance.
This can also lead to incorrect/out of date reporting of STE and average/median roughness values in ONRC and ONF Amenity Performance Measure results.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2020/21:
Metric will report the greater percentage from either the rough or hsd_rough tables.
Changes for 2021/22:
Move metric to Condition subcategory Pavement & Surfacing. Change primary dimension to Timeliness. No longer use #tempDate in the RAMM SQL.
Changes for 2024/25
Change metric to Information Only with the advent of CCDC. Change the 2.5 years to 3 years.
ROUGH2 - Roughness data has valid location
Sub-category | Pavement & Surfacing | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Information Only | |
Grade thresholds |
9598
|
The percentage of all latest roughness/HSD readings records located within the extents of the road as defined in the carriageway table.
Metric Purpose
Confirm that roughness/HSD roughness records are within the extents of the road as defined by the carriageway table.
Consequence of Poor Quality Data
If data is incorrectly located and used for analysis and reporting purposes, it may not be representative of the road section.
Records not associated with a carriageway are also not included in calculating the ONRC Amenity Performance Measure results.
Changes for 2019/20
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2020/21
Metric is to use the best result of rough or hsd.
Changes for 2021/22
Move the metric to Condition subcategory Pavement & Surfacing.
Changes for 2024/25
Change the metric to Information Only with the advent of CCDC.
FOOT4 - Footpath condition within 6 years
Sub-category | Pathways | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
7090
|
The percentage of the "in use" footpath (pathway) network length, based on footpath (pathway) sections, with a known recorded condition less than six years old at the end of the reported financial year.
Metric Purpose
Confirm that the condition data for footpath (pathway) assets is being maintained.
Consequence of Poor Quality Data
Poor condition data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor condition data could also result in the under or over valuing of assets if considered in asset valutions.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for updating the asset inventory table following condition checks. Lack of resources to maintain this dataset in a timely manner.
Changes for 2021/22
Metric created.
Changes for 2023/24
Add AMDS RAMM SQL for the metric.
Remove end date limit.
Changes for 2024/25
Only include In Use assets for AMDS.
DRAIN4 - Culvert condition within 6 years
Sub-category | Drainage System | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
7090
|
The percentage of the number of "in use" culverts (pipes) with a known recorded condition less than six years old at the end of the reported financial year.
Metric Purpose
Confirm that condition data for the culvert (pipe) assets is being maintained.
Consequence of Poor Quality Data
Poor condition data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor condition data could also result in the under or over valuing of assets if considered in asset valutions.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for updating the asset inventory table following condition checks. Lack of resources to maintain this dataset in a timely manner.
Changes for 2021/22
Metric created.
Changes for 2022/23
Use the asset owner of the drainage record rather than the owner type of the carriageway section.
Changes for 2023/24
Remove the end date limit.
Changes for 2024/25
Remove the pairing between SWC4 and DRAIN4. Only include In Use assets for AMDS.
SWC4 - Surface water channel condition within 6 years
Sub-category | Drainage System | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Low |
Grade thresholds |
7090
|
The percentage of the "in use" surface water channel (channel) length with a known recorded condition less than six years old at the end of the reported financial year.
Metric Purpose
Confirm that condition data for the surface water channel (channel) assets is being maintained.
Consequence of Poor Quality Data
Poor condition data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for updating the asset inventory table following condition checks.
Lack of resources to maintain this dataset in a timely manner.
Changes for 2021/22
Metric created.
Changes for 2022/23
Refer to the assets as surface water channels rather than kerb and channel.
Changes for 2023/24
Add AMDS SQL for the metric.
Remove end date limit.
Changes for 2024/25
Remove the pairing with DRAIN4. Chnage the importance to Low. Only include In Use assets for AMDS.
RETAIN4 - Retaining wall condition within 6 years
Sub-category | Structures | Dimension | Timeliness |
---|---|---|---|
ONRC Metric |   | Importance | Moderate |
Grade thresholds |
7090
|
The percentage of the number of retaining walls with a known recorded condition less than six years old at the end of the reported financial year.
Metric Purpose
Confirm that retaining wall condition data is being maintained.
Consequence of Poor Quality Data
Poor condition data has the potential to impact our investment decision-making, as well as hinder our understanding of the effectiveness of investment.
Poor condition data could also result in the under or over valuing of assets if considered in asset valutions.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for updating the asset inventory table following condition checks. Lack of resources to maintain this dataset in a timely manner.
Changes for 2021/22
Metric created.
Changes for 2023/24
Add AMDS RAMM SQL for this metric.
Remove end date limit.
Changes for 2024/25
Only check In Use assets for AMDS. Remove the restriction on road type so the metric just checks asset owner.
COUNT1 - Well targeted traffic count programme
Sub-category | Traffic Count | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
3040
|
The proportion of the total network Vehicle Kilometres Travelled (VKT), based on carriageway sections, with a latest traffic count record with a count date less than six years old at the end of the reported financial year.
Metric Purpose
Confirm the level of traffic demand on the network that has been recently counted and loaded into the database.
Consequence of Poor Quality Data
Poor traffic count data is likely to lead to poor traffic estimating and understanding of the current and changing demand on the network in terms of traffic volume and loading. As a result, this can also lead to inaccurate decision-making such as incorrect allocation of treatment selection.
Potential mis-categorisation of ONRC/ONF and therefore reported Network Characteristics and Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
No active traffic count strategy. Current traffic count programme not targeted at carriageway sections making up the greatest proportion of VKT. Completed traffic counts not loaded to RAMM in a timely manner.
Specific comments on the metric
The RIMS Guideline for Traffic Counting has been used to guide the grade ranges. This includes an adjustment to be carriageway section based rather than traffic links based.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2020/21:
Reduce the expected standard range to 40%. No longer use #tempDate in the RAMM SQL.
Changes for 2024/25:
Change the year limit from 5 to 6 to align with the RIMS TCE guidelines.
COUNT2 - Traffic count programme activity on sealed network
Sub-category | Traffic Count | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | Moderate | |
Grade thresholds |
1020
|
The proportion of the total network Vehicle Kilometres Travelled (VKT), based on carriageway sections, with a latest traffic count record with a count date less than one year old at the end of the reported financial year.
Metric Purpose
Confirm that count activity for the reported financial year is well targetted to understand traffic demand and is being loaded to the asset database.
Consequence of Poor Quality Data
Poor traffic count data is likely to lead to poor traffic estimating and understanding of the current and changing demand on the network in terms of traffic volume and loading. As a result, this can also lead to inaccurate decision-making such as incorrect allocation of treatment selection.
Potential mis-categorisation of ONRC/ONF and therefore reported Network Characteristics and Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
No active traffic count strategy. Current traffic count programme not targeted at carriageway sections making up the greatest proportion of VKT. Completed traffic counts not loaded to RAMM in a timely manner.
Specific comments on the metric
The RIMS Guideline for Traffic Counting has been used to guide the grade ranges. This includes an adjustment to be carriageway section based rather than traffic links based.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
COUNT3 - Traffic loading understood
Sub-category | Traffic Count | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
2030
|
The proportion of the total network Vehicle Kilometres Travelled (VKT), based on carriageway sections, with a latest classified traffic count record with a count date less than six years old at the end of the reported financial year.
Metric Purpose
Confirm that recent count data includes collecting classification (vehicle mix) so loading demand is understood.
Consequence of Poor Quality Data
Poor traffic count data is likely to lead to poor traffic estimating and understanding of the current and changing demand on the network in terms of traffic volume and loading. As a result, this can also lead to inaccurate decision-making such as incorrect allocation of treatment selection.
Traffic Cost Estimation cannot be run without a recorded traffic mix.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of active traffic count strategy with a targeted programme of classified counts on carriageway sections making up the greatest proportion of VKT. Classified traffic count data not loaded to RAMM in a timely manner.
Incomplete traffic mix data has been supplied in the count data.
Specific comments on the metric
Classified counts have been determined based on the assumption they have a recorded % cars, and no default category code in the loading method field.
COUNT3 now checks that the traffic mix (%Cars + %LCV + %MCV + %HCVI + %HCVII + %Buses) adds up to 100%.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
Changes for 2024/25
Change the year limit from 5 to 6 to align with the RIMS TCE guidance.
COUNT3 now checks that the traffic mix (%Cars + %LCV + %MCV + %HCVI + %HCVII + %Buses) adds up to 100%.
ESTIM1 - Network has traffic estimates
Sub-category | Traffic Estimates | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The proportion of the total number of carriageway section records with a recorded traffic estimate.
Metric Purpose
Confirm that all locally owned 'road' carriageway sections have a traffic estimate recorded in the asset database.
Consequence of Poor Quality Data
A lack of traffic estimates can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and ONF and therefore reported ONRC and ONF Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Poor, or lack of process for estimate traffic demand on the network. Lack of available resource for maintaining this dataset. Lack of understanding of the criticality of this dataset.
Changes for 2019/20:
Metric has been updated to exclude carriageways with a 'Not Required' ONRC.
ESTIM2a - Traffic estimates are maintained (High Volume to Arterial)
Sub-category | Traffic Estimates | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
6080
|
The proportion of carriageway sections with a latest traffic estimate record less than one year old at the end of the reported financial year where the ONRC category is High Volume, National, Regional or Arterial.
Paired with: ESTIM2b, ESTIM2c
Metric Purpose
Confirm that traffic estimates on the higher volume network are maintained in a timely manner.
Consequence of Poor Quality Data
A lack of traffic estimates can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Poor or lack of process for maintaining and updating estimate traffic demand data on the network in a timely manner. Lack of available resource for maintaining this dataset. Lack of understanding of the criticality of this dataset.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
ESTIM2b - Traffic estimates are maintained (Primary and Secondary Collectors)
Sub-category | Traffic Estimates | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
6080
|
The proportion of carriageway sections with a latest traffic estimate record less than three years old at the end of the reported financial year where the ONRC category is Primary Collector or Secondary Collector.
Paired with: ESTIM2a, ESTIM2c
Metric Purpose
Confirm that traffic estimates on the collector network are maintained in a timely manner.
Consequence of Poor Quality Data
A lack of traffic estimates can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Poor or lack of process for maintaining and updating estimate traffic demand data on the network in a timely manner. Lack of available resource for maintaining this dataset. Lack of understanding of the criticality of this dataset.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL. Improve the calculation of 3 years ago.
ESTIM2c - Traffic estimates are maintained (Access including Low Volume)
Sub-category | Traffic Estimates | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
6080
|
The proportion of carriageway sections with a latest traffic estimate record less than five years old at the end of the reported financial year where the ONRC category is Access or Low Volume.
Paired with: ESTIM2a, ESTIM2b
Metric Purpose
Confirm that traffic estimates on the lower volume network are maintained in a timely manner.
Consequence of Poor Quality Data
A lack of traffic estimates can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Poor or lack of process for maintaining and updating estimate traffic demand data on the network in a timely manner. Lack of available resource for maintaining this dataset. Lack of understanding of the criticality of this dataset.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.
ESTIM4 - Considered traffic loading
Sub-category | Traffic Estimates | Dimension | Completeness |
---|---|---|---|
ONRC Metric | Importance | High | |
Grade thresholds |
8095
|
The proportion of the total number of latest traffic estimate records with an estimated traffic loading mix distribution (i.e., not a default).
Metric Purpose
Confirm that recent traffic estimate data includes consideration of traffic mix (classification) when estimating traffic demand rather than simply using default values.
Consequence of Poor Quality Data
Not considering traffic mix can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
No process for consideration of traffic loading (mix) as part of maintaining and updating traffic estimate data. Lack of understanding of the criticality of this dataset.
Specific comments on the metric
Estimates with a considered traffic loading have been determined based on the assumption they have a recorded % cars, and no default category code in the loading method field.
ESTIM5 - Latest estimates align with counts
Sub-category | Traffic Estimates | Dimension | Accuracy |
---|---|---|---|
ONRC Metric |   | Importance | High |
Grade thresholds |
7090
|
The proportion of carriageway sections where the latest estimated AADTs are within +/-30% or +/-50vpd (whichever is the greater) of the latest counted ADT within the last five financial years.
Metric Purpose
Confirm that estimated AADTs are within thresholds of the latest counts.
Consequence of Poor Quality Data
Potentially inaccurate traffic estimates can hinder understanding network demand, including changing demand, for analysis and planning purposes.
Potential mis-categorisation of ONRC and therefore reported ONRC Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
No process for verification of calculated traffic estimate data. Lack of understanding of the criticality of this dataset.
Specific comments on the metric
+/-30% or +/-50vpd of count (whichever is the greater) variations are considered to be sufficient thresholds to indicate a significant variation between counts and AADT estimates
Changes for 2021/22
Metric created. Does not include any counts with confidence set to zero (0).
CRASH1 - Crash data is recent
Sub-category | Crash Data | Dimension | Timeliness |
---|---|---|---|
ONRC Metric | Importance | Moderate | |
Grade thresholds |
126
|
The age (in months) of the most recently loaded crash data in terms of the time difference between the date added to RAMM and the date loaded into REG Insights.
Metric Purpose
Confirm that crash data is being maintained and updated in RAMM by the RCA in a timely manner.
Consequence of Poor Quality Data
An incomplete dataset could be used for wet crash analysis associated with skid management processes, resulting in inaccurate decision-making.
ONRC and ONF Safety Performance Measures results could be impacted by having an incomplete dataset through not being updated/maintained frequently.
Potential reason(s) for not being at the expected standard unique to this metric
Lack of awareness of the process to maintain this dataset in RAMM. This data is not used to analyse or report on crashes on the network. Lack of resources to maintain this dataset.
Specific comments on the metric
The time difference between latest added on date in RAMM and the date imported into REG Insights has used a proxy to measure the timeliness of updates to this dataset.
Changes for 2024/25
Report 0 months when running the query with crash data in the following year.
CRASH2 - Crash records with valid location
Sub-category | Crash Data | Dimension | Accuracy |
---|---|---|---|
ONRC Metric | Importance | Moderate | |
Grade thresholds |
9598
|
The proportion of the total number of crash records located within the extents of the road, as defined in the carriageway table, for the five year period up to the end of the reported financial year.
Metric Purpose
Confirm that crash data in RAMM is within the extents of the road as defined in the carriageway table.
Consequence of Poor Quality Data
An incomplete dataset could be used for wet crash analysis associated with skid management processes, resulting in inaccurate decision-making.
Any crashes outside of a carriageway section are not included in the ONRC and ONF Safety Performance Measures results.
Potential reason(s) for not being at the expected standard unique to this metric
Data not imported to RAMM through correct processes. Network updates not completed through correct processes (RAMM Network Manager) resulting in affected tables not being updated.
Changes for 2021/22
No longer use #tempDate in the RAMM SQL.