Upload
others
View
6
Download
0
Embed Size (px)
Citation preview
Specification for Road Condition Data Collection Services
Specification for Road Condition Data Collection Services
TABLE OF CONTENTS
1 INTRODUCTION..........................................................................................................4
2 OBJECTIVES................................................................................................................42.1 Objectives of the Services......................................................................................42.2 Procurement Process.............................................................................................4
3 GENERAL CONDITIONS ............................................................................................53.1 Terminology............................................................................................................53.2 Roles of the Parties to the Contract.......................................................................63.3 Term of the Contract..............................................................................................63.4 Survey Suppliers....................................................................................................63.5 Data to be collected ...............................................................................................73.6 Survey Network......................................................................................................83.7 Special Instructions................................................................................................93.8 Survey Header Data...............................................................................................93.9 Survey Equipment..................................................................................................93.10 Contractor Skills.................................................................................................103.11 Survey Procedure...............................................................................................103.12 Location Referencing System (LRS)..................................................................113.13 Equipment to be Provided by Client...................................................................113.14 Equipment to be Provided by Contractor............................................................113.15 Data Format.......................................................................................................11
4 DATA COLLECTION SPECIFICATIONS....................................................................124.1 Location Referencing...........................................................................................124.2 GPS Centerline Coordinates ...............................................................................134.3 Geometry..............................................................................................................144.4 Right of Way Video...............................................................................................144.5 Condition..............................................................................................................15
5 CALIBRATION AND VALIDATION.............................................................................175.1 Calibration – Methodology ...................................................................................175.2 Validation – Methodology.....................................................................................185.3 Roughness...........................................................................................................195.4 Rutting..................................................................................................................205.5 Texture Measurement (Mean Profile Depth)........................................................205.6 Road Geometry – GPS........................................................................................215.7 Right of Way Video...............................................................................................225.8 10 km Field Validation..........................................................................................22
6 QUALITY CONTROL AND ASSURANCE..................................................................236.1 Quality Management Plan....................................................................................236.2 Data Display.........................................................................................................246.3 Data Backup.........................................................................................................256.4 On-going Validation..............................................................................................25
100824 Data Collection i
Specification for Road Condition Data Collection Services
7 TRAFFIC MANAGEMENT AND SAFETY...................................................................257.1 Health and Safety Compliance Notice..................................................................267.2 Health and Safety Compliance Notice..................................................................267.3 Traffic Management Plan.....................................................................................27
8 DATA PROCESSING AND STORAGE......................................................................278.1 Data Format.........................................................................................................288.2 Providing Data......................................................................................................288.3 Data Review and Acceptance..............................................................................28
9 MONITORING AND REPORTING..............................................................................299.1 Initial Meeting.......................................................................................................299.2 Quality Management Plan....................................................................................299.3 Final Report..........................................................................................................29
10 KEY DELIVERABLES...............................................................................................3010.1 Deliverables........................................................................................................3010.2 Format................................................................................................................3010.3 Intellectual Property............................................................................................31
11 SCHEDULE AND RESOURCES..............................................................................3111.1 Project Schedule................................................................................................3111.2 Data Collection Contractor’s Personnel..............................................................31
12 BASIS OF PAYMENT...............................................................................................3112.1 Basis of Payment...............................................................................................3112.2 Payment.............................................................................................................32
100824 Data Collection ii
Specification for Road Condition Data Collection Services
Abbreviations
DCC Data Collection ContractorDGPS Differentially corrected Global Positioning SystemGPS Global Positioning SystemID IdentificationIRI International Roughness IndexLRP Location Reference PointLRS Location Referencing SystemMPD Mean Profile Depth NAASRA National Association of Australian State Road AuthoritiesQMP Quality Management PlanRAMM Road Assessment and Maintenance ManagementRCA Road Controlling AuthorityRMSD Root Mean Sensor Texture Depth SLP Stationary Laser ProfilerTMP Traffic Management PlanRMS Road Management SystemRTRMS Response Type Roughness Measuring Systems
100824 Data Collection iii
Specification for Road Condition Data Collection Services
INTRODUCTIONCondition assessment is a key road network performance measure and a major determinant of road users costs. It is used in pavement management systems for monitoring the network’s condition and predicting its future condition. Condition data is used as an input to support efficient and effective road network asset management decisions. . It is also one of the primary indicators used in network level maintenance programming, monitoring network performance, managing the term maintenance contracts, benchmarking among Road Controlling Authority (RCA) networks, and undertaking research and fatal crash investigations. Therefore, it is essential the condition data is of a high standard.
This manual focuses on pavement condition survey collection. Of the many techniques and equipment used in measuring roughness and rutting, those of particular interest to RCAs are the ones that provide versatility, speed and minimum disruption to road users.
Automated non-contact profilometers collect the longitudinal and transverse profile data used to calculate roughness, rut depth and other condition parameters while operating at high speed. The longitudinal road profile is summarised by the International Roughness Index (IRI) and converted to (National Association of Australian State Road Authorities (NAASRA) to give lane roughness in counts/km a format familiar to practitioners in New Zealand. The transverse profile measurement provides the depth and extent of rutting in the wheel paths.
This manual can be used by any road agency as a basis for developing a set of data collection specifications. The agency will only select the equipment and facilities considered necessary to satisfactorily complete the measurements on their network. It is intended for both network level and project level surveys, and includes the minimum specifications required to achieve an acceptable level of accuracy and repeatability. This will give those undertaking on-going analysis for network maintenance and upgrading confidence in the data's veracity.
1 OBJECTIVES1.1 Objectives of the Services
The data collection services provide a means for collecting accurate and repeatable pavement condition data which will assist <insert Client name> in defining the road network's true condition. It will be used to:
Provide network condition data to identify annual changes in the network's condition and to help with planning road management and investment strategies.
The data collection service provider will be required to provide data in a suitable format for uploading into the client's road management database.
1.2 Procurement ProcessThe procurement process shall be as follows:
The bids shall be opened and reviewed according to <insert Client name> bid evaluation process and the successful applicant will be
Data Collection Specification4
Specification for Road Condition Data Collection Services
informed in writing that they have been awarded the contract. The Data Collection Contractor (DCC) shall mobilize their team
according to the terms of the contract. Written agreement to advance with the full survey shall only be issued
after the validation study has been successfully completed If the data fails to meet the client's specifications, the DCC shall be
given 30 days to rectify the situation at <insert Client name> sole discretion.
2 GENERAL CONDITIONS2.1 Terminology
Automated Data Collection: fully automatic data measurement and storage using electronic or mechanical measurements (e.g. profilometer measurements)
Semi-Automated Data Collection: manually collected observations are digitally recorded (e.g. keyboard rating or voice recording of surface defects)
Manual Data Collection: manually collected observations are written down and later digitally recorded via keypunch operators (e.g. walk-over manual survey using data entry form and clipboard)
Road Network: a logical system of road links, segments and nodes. Location Reference Point (LRP): these are placed at intermediate
points between nodes. An LRP is a permanent object on or adjacent to the road which has been accurately located in terms of geo-coordinates and is used as a reference point for distance measurements
Accuracy: the survey equipment's ability to measure the true condition of the item being surveyed. The aim is to reduce equipment-related bias or errors.
Measurement Interval: the physical measurement interval used by the equipment (e.g. roughness measurements using laser profilometers record and store the measured profile every 25 mm)
Reporting Interval: the minimum specified reporting interval at which the data is summarised (e.g. roughness may be reported at 10 m, 20 m, 50 m, or 100 m intervals)
Dual Carriageway Road: a multi-lane road with or without a barrier or median separating traffic travelling in opposite directions
Split Road: a road segment, which is split at a particular location from a single carriageway to dual/parallel carriageway
Surface Area: the total section length multiplied by the carriageway width, excluding the paved shoulder width.
Data Collection Specification5
Specification for Road Condition Data Collection Services
2.2 Roles of the Parties to the Contract
Client - the asset owner for whom the data is being collected, <modify to suit>
Data Collection Contractor (DCC) - normally responsible for data collection, data processing and quality assurance.
2.3 Term of the Contract
The Contract term is xyz.
2.4 Survey Suppliers
Several organisations in New Zealand have vehicle-based laser equipment and/or response type roughness measuring systems (RTRMS) available for measuring roughness and rutting.
Table 1.1: Vehicle-based Laser and Response Equipment Survey Suppliers as at 1 April 2011
Survey Suppliers Organisation Location Measurements Contacts
Downer EDI Works
397 McLeans Is Rd.
RTRMS - Roughness
C Bycroft Ph. 03 359 0752
Fugro PMS31 McKee St Hamilton
Laser Profiler /Scanning Laser; Roughness, Rutting, Skid Resistance, Video, GPS.
D Scruby Ph 07 847 0499 www.fugropms.co.nz
Opus International Consultants
7A Ride Way Albany Auckland
RTRMS - Roughness
L Ash croft Ph 09 415 4660Episcopalian
Opus International Consultants
200 Frying St Dunedin
RTRMS - Roughness
D Searcher 03 477 9173Episcopalian
Road Info 25 Edwin St Paeroa
Roughness – Laser Profiler
Erik Kruithof Ph. 07 862 9150
Shaw’s Consulting Services Ltd
60 Tukapa St New Plymouth
Roughness – Laser Profiler
Chris Shaw Ph 06 753 [email protected]
WDM, UK Ltd. United Kingdom and New Zealand
Laser Profiler; Roughness, Rutting Skid Resistance, Video,
D Newlands Ph 04 233 6221 www.wdm.co.uk
Data Collection Specification6
Specification for Road Condition Data Collection Services
GPS
2.5 Data to be collected
The following data is must be collected for this contract. ( <Client to modify to suit/select as appropriate>)
Data Item Units Reporting Interval
Minimum Accuracy Level
Paved Unpaved
Location ReferencingLocation referencing (points)
- See Section 3.1 1 m M M
Location Referencing (linear)
- See Section 3.1 0.1% M M
GPS Centreline Coordinates
- See Section 3.2 1 m - horizontal2 m - vertical
MM
MM
Geometry - See Section 3.33 <modify include or delete to suit specific requirements>.
Horizontal Alignment
O/km 1000 m IQL 2 paved – 5%
IQL 4 unpaved
M M
Vertical Alignment
m/Km & No/km
1000 m IQL 2 paved – 5%
IQL 4 unpaved
M M
Multi Media - See Sections 3.4 Right Of Way (ROW) Video Logging
- Continuous/1 m/5 m/10 m
800 x 600 pixel
M M
Digital Images of LRPs
- 5 megapixels
M M
Digital Images of Bridges
- 5 megapixels
M M
M – Mandatory; O – Optional; NR – Not Required.
The DCC should refer to Section 2.15 and Chapter 4 for details of data collection formats and specifications. The DCC should note that data must be collected so it can be presented in both the formats described below.
Data Collection Specification7
Specification for Road Condition Data Collection Services
2.6 Survey Network
The road network distribution by pavement type:
<Client to define/include network details as appropriate>
RegionPaved Road km
Unpaved Road km Total
2.7 Special Instructions
The DCC's should consider the following issues when preparing their proposal.
Client to specify
The special issues above are given for information purpose only and DCC shall source the information required to prepare their proposal.
2.8 Survey Header DataThe following items must be recorded with or linked to each of the specific data items detailed in Section 3.5 to 3.7:
Survey date and time of day Description of section Vehicle ID, Crew ID Weather conditions Average travel speed Direction of survey relative to reference direction
(increasing/decreasing) Lane number or transverse position on road (where applicable).
2.9 Survey Equipment
The DCC is free to use their own choice of equipment to collect the specified data. The equipment selected must be capable of recording
Data Collection Specification8
Specification for Road Condition Data Collection Services
data to the specified levels of accuracy (refer to Table 3.5 above). All survey equipment used for data collection should be fully
functional at the normal local highway speed under the conditions to be encountered on the <paved and unpaved road> <select as appropriate> networks.
The DCC should only use the latest versions of the software released by the equipment manufacturers.
The DCC must disclose the algorithms used for all relevant equipment and software that will be used in the survey (e.g. the profile processing algorithms that will be used by the proposed laser profilometer for calculating roughness).
All equipment and software proposed by the DCC will be subject to Client approval.
2.10 Contractor Skills
The DCC must demonstrate that their staff have the required training and experience to use their assigned equipment and to undertake the work described in these TOR.
Survey staff competency will be assesses and approved during the equipment calibration and validation process.
The DCC must ensure their staff are trained or skilled in all policies and work practices adopted by <insert Client name> (traffic control requirements, road safety, health and safety practices).
2.11 Survey Procedure
If the DCC chooses to use more than one survey vehicle or to complete the surveys in multiple passes, the selected survey process must demonstrate that all data can be matched to the same road furniture and road features. The DCC must also provide <insert Client name> with details on how the surveys will be conducted and in which order.
On single lane roads all surveys are to be conducted in the direction of increasing km post. Irrespective of the survey direction, all data are to be referenced in terms of increasing km post and chainage.
The standard survey procedures shall be:
On narrow single carriageway roads the survey vehicle must travel in the direction of increasing chainage, with the measurements taken in the normal driven wheelpath. Note where roads are particularly narrow this is likely to straddle the road centre-line. Data processing techniques should account for instances when the vehicle deviates from the road onto the shoulder.
On single carriageway, two-lane roads the DCC will survey both increasing and decreasing lanes. The measurements will be taken in the wheel paths; where no obvious wheelpath is visible the measurements will be taken 50 to 70 cm from the edge of the pavement.
Data Collection Specification9
Specification for Road Condition Data Collection Services
On divided carriageway roads and service lanes the DCC will survey both increasing and decreasing lanes (both carriageways and service lanes). The measurements will be taken in the wheel paths; where no obvious wheelpath is visible the measurements will be taken 50 to 70 cm from the edge of the pavement.
On dual carriageway roads the DCC will survey both increasing and decreasing lanes (both carriageways). The measurements will be taken in the most heavily trafficked wheel paths; where no obvious wheel path is visible the measurements will be taken 50 to 70 cm from the edge of the pavement.
Where GPS coordinates are specified the DCC will ensure the coordinates are offset to obtain the road centreline.. Note the DCC must gain the client's approval for the method chosen for this offset.
Other - <Client to specify; this could include additions or variations to the conditions above >
Data collection activities should not be undertaken when the road surface is wet or contaminated with debris unless the equipment can be demonstrated to meet the validation criteria for these conditions.
2.12 Location Referencing System (LRS)The DCC will <use the existing/be required to establish a new Location Referencing System (LRS)><select as appropriate>.This system will rationalize and replace the existing system, and will include the following details3.1:
Area Road identity (I/D) Carriageway start and end Km Reference (chainage from start of link).
<modify to suit>More detail about the LRS is given in Section 3.1 and Annex 1
2.13 Equipment to be Provided by Client
The Client will not provide any survey equipment.
2.14 Equipment to be Provided by Contractor
The DCC will list all the equipment needed to complete the survey in their proposal, and provide it. The DCC shall also state the number of sets of equipment they intend operating simultaneously.
The DCC's proposed methodology shall clearly demonstrate that the listed equipment is capable of producing the types and quality of information that will satisfy the requirements set out in Chapter 3: Data Collection Specifications.
Notwithstanding the client's acceptance of equipment the DCC proposes, the DCC is wholly responsible for providing data that meets the technical specifications.
Data Collection Specification10
Specification for Road Condition Data Collection Services
2.15 Data Format
All data must reflect the standard practice of driving on the left. All data algorithms must be agreed by the client. All GPS data must be calibrated to the NZGD2000 transverse
Mercator/other local Mercator <modify to suit>. Two levels of data are required – raw data, and detailed data:
Raw data is the record of the individual measurements taken by the survey equipment. It must be provided in ASCII delimited format or a format agreed by the client. Raw data detail must be retained so the detailed and aggregated data can be recalculated.
Detailed data is processed raw data summarised at 20 and 100 m intervals.
The equipment shall be able to produce export files in an industry standard format e.g. comma separated values and MS Excel.
A full description of the data reporting interval and format for each data type is detailed in Chapter 4.
When data is to be loaded into the <modify to suit> RAMM database the DCC shall note:
The data will be stored in the Client database. This was supplied by …….. and includes the following modules <modify to suit>
Information System or Viewer of Network Periodic Maintenance of roads Routine Maintenance of roads Traffic Module and traffic data analysis.
3 DATA COLLECTION SPECIFICATIONS3.1 Location Referencing
The Client will provide the DCC with the existing nodes and LRPs with their offset chainage in one of the following ways:
Digitally in .dbf / .mdb / text <modify to suit> format. The DCC must use this information when collecting other specified data items
By granting the DCC access to their RAMM database so the DCC can extract the necessary information themselves.
The DCC must measure the distance and offsets when other data is collected. The allowable distance measurement error is 0.1%. Therefore two possible scenarios exist:
Where there is a discrepancy in distance measurement, but it is within the allowable error limit, the measurements shall be appropriately scaled to match the total length provided by the Client. This scaling factor shall be determined for each <road / link / measurement unit> <modify to suit>
Data Collection Specification11
Specification for Road Condition Data Collection Services
and this factor shall be used to scale the length within the road/link/measurement unit <modify to suit>.
Where there is a discrepancy in a distance measurement and this exceeds the allowable error, the DCC must re-survey the road/link/ measurement unit <modify to suit>. If the second survey confirms the initial survey, the DCC must notify the Client immediately. The DCC must confirm the current distance measuring instrument's accuracy; where this is within tolerance the DCC may continue the survey. If the distance measuring instrument is not within tolerance, the DCC must develop a remedial proposal the Client agrees with.
If the distance discrepancy remains consistent on other links the Client will consider establishing a new set of location referencing data.
The DCC must provide the Client with detailed information about their equipment capability in handling pre-defined location referencing data.
<modify to suit>
The following provide the DCC with the Client's definition of measurement accuracy for distance and GPS centerline coordinates.
Distance MeasurementThe distance measurement instrument transducer must be installed on the survey vehicle so the distance measurement replicates the road centerline (on the wheel nearest to the road centre). This will minimize loss of accuracy during turning movements.
All distances shall be measured using a distance measurement device with an accuracy of 0.1% or better.
The positions of LRPs and other important marks (e.g. intersections, bridges, culverts, railway crossings) shall be expressed as distances from the previous node. Chainages are measured continuously from the start to the end of the link. At each node the distance must be reset to 0. In this way, all distances will be expressed as the distance from the previous node.
3.2 GPS Centerline Coordinates
<modify/include as required>The road centerline is a notional reference line that generalises (to an accepted and known accuracy) and approximates the true centerline.
The raw/differentially corrected <modify to suit> geo-coordinates of the nodes, LRPs and centerline shall be recorded and reported. The data are to be provided in the NZGD2000<modify to suit> mapping coordinate system, which can readily be imported into ArcView and ArcGIS.
Differentially CorrectedThe geo-coordinates shall be measured using either real time Differentially corrected Global Positioning System (DGPS) equipment, or equipment that is post processed for differential correction. The differentially corrected data must
Data Collection Specification12
Specification for Road Condition Data Collection Services
attain the following accuracy standards: 95% of data accurate to ± 1.0 metre horizontally and ± 2.0 metre vertically. The DCC must specify the differential correction data source and methodology they propose to use.
The GPS referencing should be made as close to the road centerline as is practical. The altitude reference must be made at the pavement surface, and the DCC must supply the geo-coordinates at intervals of not more than 10.0 meters at the road centerline; the intervals must be sufficient to locate all required features and road geometry to the specified level of accuracy. If the carriageway is divided, the location data will be the same as that used to describe the carriageway centerline. All centerlines must have the correct and complete topology (e.g. intersecting roads must intersect) and a unique centerline must be provided for each link.
The DCC's technical proposal must describe the methodology they propose using to establish the road centerline. This shall include discussions on:
How the data will be collected Real-time or post-processed differential correction method Correction of data anomalies (e.g. loss of GPS signal, gyro drift over time,
satellite downlink DGPS, differences between measured and GPS-derived lengths, avoidance of obstacles etc.)
Data processing, and its reconciliation with LRP survey co-ordinates.
3.3 Geometry
The required geometric data is specified in the following table. It must be reported in a format compatible with HDM IV/other RMS <change as required> as detailed in Table 4.4.
The data may be obtained from the GPS data provided it meets the required specifications. <delete if not required>
Data Type Parameter to Report
Units Accuracy Reporting Interval (m)
Horizontal Alignment
Average horizontal curvature of the road per km
º/km 5% 100
Vertical Alignment
Average absolute rise + fall per km
m/km 5% 100
Average number of road rises and falls per km
No/km 5% 100
Table 4.4 Road Geometry Specifications
Data Collection Specification13
Specification for Road Condition Data Collection Services
3.4 Right of Way Video
Right of Way VideoChainage-synchronised right-of-way digital images with a minimum resolution of 600x800 <change as required> pixels must be captured at 10 m intervals. The images must be compressed and stored in JPEG format. Although the data may be collected as either a continuous or time or frame based system, preference will be given to methodologies using continuous data.Location identification information superimposed on each frame must include:
The road number The link reference The chainage.
The image filenames must include the road number and chainage.
A playback system which facilitates the easy review and location identification of specific road sections must be provided. <delete if not required>
3.5 Condition
Pavement Roughness: Laser Profilometer <delete if not required>
The DCC must use a non-contact laser profilometer to measure the paved roads' longitudinal profile. The profilometer should conform to the ASTM E950-94 standard, have a vertical resolution of less than 0.1 mm, and achieve a roughness measurement accuracy of< 0.1 mm. The DCC shall record and report the longitudinal profile data and process the profile data to provide and report International Roughness Index (IRI) in m/km. The lane roughness calculations are made from the average of the left and right wheel path profiles, and the data recorded and reported as follows:
Number of wheel paths: two Longitudinal profile sampling interval: no more than 25 mm IRI reporting interval: 20 m and 100 m NAASRA Counts interval 20 m and 100 m.
Factors which may influence the IRI must be recorded during the survey and the data corrected accordingly. These factors include, for example, survey speed in congested areas, traffic congestion, pavement construction activities, and having to travel off the carriageway.
Some operational practices, such as sudden acceleration or braking during surveys, may also influence the IRI and operators should avoid these. In these cases where data quality is compromised the DCC must notify the Client of the affected sections, explain the reasons for the poor data quality and propose remedial actions. Remedial actions may include doing a manual assessment of the roughness, or re-surveying the sections at a different time.
Pavement Roughness – Response Type Roughness Meter <delete if not required>
Data Collection Specification14
Specification for Road Condition Data Collection Services
The roughness data must be collected using a single/dual <modify to suit> response-type roughness meter/s or similar, with the instrument calibrated to the IRI expressed in m/km in accordance with ASTM E 1448-92/98. The roughness data must be reported at 20 m and 100m intervals, and the speed recorded during the survey and taken into account when calculating the IRI from the raw data.
Factors which may influence data quality must be recorded during the survey and the data corrected accordingly. These include, for example, traffic congestion, pavement construction activities and having to travel off the carriageway.
Rut Depth: <delete if not required>
The transverse profile is to be measured using non-contact sensors covering both wheel-paths of a lane. The rut depth is to be expressed as the maximum vertical depth in mm for each wheel path under an equivalent 2.0 m straight edge, and the data recorded and reported as follows:
Measuring width no less than 3200 mm Vertical resolution 0.5 mm Minimum number of measurements per profile 13 Distance between measurement locations across profile 200 mm to
400 mm Longitudinal sampling interval of 2 m or less Reporting interval 20 m Data to be reported as mean and standard deviation of left and right
wheelpath rut depth Readings shall be corrected in order to eliminate the effects of the
vehicle suspension movements and to establish a reference level for the profile measurements.
The maximum rut depth in each wheel path must be obtained from the transverse profiles using a 2.0 m straight edge simulation programme.
The DCC's technical proposal must describe their system's configuration, and disclose the data processing algorithm.
Surface Texture <delete if not required>
The texture will be calculated for each wheel path using non-contact sensors. The macro texture will be presented as the Root Mean Sensor Texture Depth (RMSTD) and/or the Mean Profile Depth (MPD) and reported as the average depth (in mm):
Reporting interval 20 m and 100 m intervals. Vertical resolution 0.01 mm Minimum sampling interval 0.5 mm.
Crossfall/ Super-elevation: Paved Roads <delete if not required>
The transverse gradient (camber or super-evaluation) of paved roads shall be recorded for each lane using electronic inclinometers attached to the rut bar and corrected for the movement of the vehicle with an accuracy of <0.5%. The data
Data Collection Specification15
Specification for Road Condition Data Collection Services
must be recorded and reported as follows:
Measuring width no less than 3,200 mm Vertical resolution 0.5 m Longitudinal sampling interval of 2 m or less Reporting interval 20 m Readings must be corrected to eliminate the effects of the vehicle's
suspension movements and to establish a reference level for the profile measurements.
The DCC's technical proposal must describe their system's configuration and also disclose the data processing algorithm to the Client for approval.
4 CALIBRATION AND VALIDATION4.1 Calibration – Methodology
DCC's must comply with the following calibration methodology: Calibration by correlation with other vehicle mounted survey
equipment should not be used1. A Class 1 reference profilometer must be used to provide the reference profile data.
All the measuring equipment's calibration certification must comply with a recognized international standard
The calibration certification will confirm individual equipment accuracy as defined in section 4 for the system's measuring components like the accelerometers, the lasers and the distance measuring system
If equipment is replaced during the contract it must be calibrated exactly as the original equipment was at the start of the contract
The DCC must specify the period for recalibrating each item of equipment during the course of the contract.
1 The exception to this is when the equipment being validated is less accurate than the vehicle mounted system it is being validated against. For example, a response-type roughness meter can be validated against a laser profilometer.
Data Collection Specification16
Specification for Road Condition Data Collection Services
4.2 Validation – Methodology
DCC's must comply with the following validation methodology: Validation operations should be recognised as separate processes within the overall objective of obtaining accurate and reproducible roadway profilers A validation programme should be carried out prior to accepting the equipment; it may also begin before data collection activities start Continued measurement validation must be carried out during and at the completion of data collection activities A minimum of four sites, each 300 m long, should be used for roughness, and four sites each 200 m long for both geometry and rut depth; these will be selected to reflect the full range of operating conditions likely to be encountered in the surveys A post survey validation should be carried out when the overall survey is completed
Regardless of when equipment is replaced during a contract, it must be revalidated, just as it was at the start of the contract.
Validation ApproachThe survey equipment must be validated at each site against a reference measurement. This is done by measuring sections of roads with the reference instrument, and then the same sections with the survey equipment.
For roughness calibration equipment must be compatible with ASTM standard E950 (2004) ‘Standard Test Method for Measuring the Longitudinal Profile of Travelled Surfaces with an Accelerometer Established Inertial Profiling Reference’, Class I.
The survey equipment must make at least five repeat runs over each of the validation sections at three nominal speeds of 25, 50, and 75 km/hour or within the limits specified by the manufacturer. The results must be averaged to give the profile at each of the nominated speeds.
The line of best fit between the reference measurement and the survey equipment using least squares regression is then established:
RM = SE x A + B
Where:
RM = The measurement from the reference equipment
SE = The measurement of the survey equipment
A = Slope of line of best fit
B = Intercept of line of best fit (regression offset).
The equipment is considered validated when A and B, and R2 (the co-efficient of determination) are within the specified parameter ranges detailed in Table 1 below for all sites combined.
Repeatability – this is the expected standard deviation of measurements obtained
Data Collection Specification17
Specification for Road Condition Data Collection Services
in repeat tests, using the same survey equipment on a single randomly selected road. The standard deviation of measurement on each segment must be within the tolerance defined for the different surface types from the mean for each of the five rrepeat runs.
Assuming a normal distribution then the 95% confidence intervals for the
measured parameter is given by: .
Where:
data = The data measured by the instrument (e.g. IRI m/km, mm rut depth, etc.)
s = The standard deviation of the data in the same measurement units
n = The number of runs
t = 2.776. This is the critical value for the t Distribution for a Critical t Confidence Interval of 95%. For further information, see Modern Data Analysis - A First Course in Applied Statistics, Hamilton LC, 1990.
The equipment is considered to be repeatable when it is within the specified percentage of the mean, as shown on Table 1 below2.
Table 1: Validation Limits
Parameter Slope(A)
Intercept(B)
CorrelationR2
Acceptance Limit
Laser Profiler Roughness
0.98–1.02 0.2IRI > 0.98 < 0.10 IRI
Response Type Roughness
Not Applicable
0.5IRI > 0.93 < 0.30 IRI
Rutting 0.95–1.05 0.5 mm > 0.97 < 0.050 RD
Texture 0.95–1.05 0.2 mm > 0.95 < 0.10 MPD
4.3 Roughness
Setting the reference profile: The base road surface profile over the validation sections must be measured using a reference Class 1 profiler. The reference profiler is used to record each profile over the full validation length. Each wheelpath must be measured at least twice; and the average of the individual readings measured in each wheelpath will provide the reference profile.
2 These levels are designed for roads in good to fair condition (e.g., IRI<5m/km). If the roads are in poor condition then the tolerances may be relaxed.
Data Collection Specification18
Specification for Road Condition Data Collection Services
Interrupted data collection – interrupted data must be validated by:
Driving over the validation sections at varying speeds during each run and achieving the same repeatability when compared to the constant speed run
Demonstrating the effects of ‘stop and go’ and the effectiveness of the equipment for handling survey interruptions such as slow traffic, for example).
4.4 Rutting
Rut depth definition – this is defined as the height between the pavement and a user defined straight edge placed across the rut, i.e. the distance obtained from the manual straight edge and wedge methodTo obtain the Measurement Location – the profile (crossfall) and rut depth measurements are taken at five m intervals along each 200 m section.
The DCC may choose to validate the surface profile and rut depth by using either reference profiles or straight-edge and wedge.
Using Reference ProfilesSetting the reference profile – the reference transverse profile on each of the validation sections must be measured using either a reference profile beam or surveyor rod and level, or another approved method. The method adopted must be capable of measuring the transverse profile at 100 mm intervals to a vertical accuracy of ±0.25 mm.
Validating the reference profile – transverse profile graphs for both the reference profile and the survey equipment for each speed must be provided to demonstrate that the equipment is measuring the true pavement transverse profile.
Using Straight-Edge and WedgeEstablishing the reference rut depth – The rut depth on each of the validation sections is measured in both left and right wheel paths to an accuracy of ±0.5 mm at five m intervals along each 200 m section.
Validating the rut depth – The survey equipment must be validated at each site against the reference rut depth derived from the straight edge and wedge; if a reference profile beam is used instead, the rut depth is calculated from the reference profile.
4.5 Texture Measurement (Mean Profile Depth)
Texture is defined as the mean measure of the texture depth over a discrete 100 mm length of pavement.
Establishing the measurement location – texture depth measurements are taken at five m intervals along each 200 m section.
The DCC may choose to validate the texture depth by using either reference profiles (using the NZTA Stationary Laser Profiler (SLP)) or by using the manual
Data Collection Specification19
Specification for Road Condition Data Collection Services
volumetric texture (sand patch) method.
Using the SLP Reference DeviceSetting the reference profile – the reference texture depth on each of the validation sections must be measured using the NZTA SLP or another approved method. The method adopted must be capable of measuring the texture depth to a vertical accuracy of ±0.025 mm.
Using the Volumetric (Sand Patch) Texture MethodEstablishing the reference texture depth – the texture depth on each of the validation sections is measured in both left and right wheel paths to an accuracy of ±0.1 mm at five m intervals along each 200 m section.
Validating the texture depth – the survey equipment must be validated at each site against the reference texture depth derived from the manual sand patch method or from the reference texture device (i.e. the NZTA stationary laser profilometer).
4.6 Road Geometry – GPS
Road CentrelineThe road centreline should be validated both statically and dynamically:
Static validation – static validation is determined by taking stationary measurements at a local datum, or at location which has been accurately established by registered surveyors. A minimum of ten measurements are taken and compared to the true location.
Dynamic validation – the survey equipment should be driven at normal survey speed and survey mode. At the same time it should record road centreline coordinate data through a loop section of not less than five km containing at least five of the 10 reference locations. Coordinate data for each reference point should be flagged as the vehicle passes the reference point, and extracted from the data stream. The loop runs should be made over two days at different times.
The equipment operator must also demonstrate that the inertial system can compensate for loss of GPS signal.
Validation will be confirmed when:
All static measurements are within 0.5 m of the true location All dynamic measurements are within 1 m of the true location The equipment is able to demonstrate that GPS signal loss does not
degrade data quality from that specified above Repeat loop runs demonstrate that the spread of data is not greater
than 5 m at any one location within the loop.
4.7 Right of Way Video
The Client will review the quality of the right of way video presented in the 10 km trial (Section 4.8) and then confirm their acceptance of this.
Data Collection Specification20
Specification for Road Condition Data Collection Services
4.8 10 km Field Validation
When the calibration and validation is complete, each system will be used to carry outs 10 km of field surveys in line with the following Austroads Test methods: AG:AM/T004 Pavement Roughness Repeatability and Bias Checks for an Inertial Profilometer, and AMT12:2005 Pavement Rutting Verification Tests for Multi Laser Profilometer. This field survey will cover a range of roads and operating conditions representative of those on which the surveys will be undertaken. To undertake the field validation, the DCC will ensure:
The equipment is operated in the same manner as when actual surveys will be undertaken
The data from the equipment is processed to produce outputs consistent with this specification's requirements.
The DCC must either import the processed data to the Client's Road Management System, or alternatively show their equipment can export data in an open format which is consistent with Client requirements.
Data Collection Specification21
Specification for Road Condition Data Collection Services
5 QUALITY CONTROL AND ASSURANCE5.1 Quality Management Plan
The DCC shall prepare a detailed Quality Management Plan (QMP). The QMP is expected to ensure the required data acquisition meets the Client's needs and specifications. The QMP has to address, among others, the following issues:
Schedule of deliverables Risk management profile Contingency plans Personnel and responsibilities Information management Equipment
In addition the QMP must incorporate information demonstrating: The equipment/system design, specifications and configuration will
meet the Client's needs Compliance monitoring will be undertaken using equipment capable of
delivering the outcome according to contract specifications (including calibration and validation processes)
Knowledge of and access to the manufacturer’s recommended spare parts so equipment can be repaired
How they will identify and deal with random, operator and systematic errors
How they will ensure all measuring devices are functioning properly on a regular basis (via daily checks and calibration)
Their survey procedures, particularly with regard to the way they handle narrow roads, work zones, and any other unusual conditions
Their procedures for restricting surveys in conditions such as poor weather or heavy traffic
How slow speed conditions will be handled during surveys and what actions they will take in the event of data gaps due to the instruments inability to record accurately under these conditions
How they will conduct the survey in the order of decreasing chainage and how the data will be reconciled
How the surveys will ensure correct location referencing, particularly in handling the case of missing km posts, or inaccurate lengths between consecutive km posts
Explaining their operating procedures and data correction processes for travel on narrow roads, or pavements with severe distresses (e.g. potholes/corrugations)
Their contingency plans, to ensure there are allowances and processes in place for back-up equipment, systems and staff.
Data Collection Specification22
Specification for Road Condition Data Collection Services
The DCC will incorporate data processing and management into their QMP showing:
Their data processing procedures and algorithms How their system will prevent or manage file corruption, viruses, and
similar problems with digital equipment Their data acquisition procedures and media for acquiring long-term
raw data and other large data volumes Software versions and how to keep track of software changes Their data security measures and systems to ensure data safety,
security, and redundancy in the event of catastrophic failure or destruction of data storage facilities.
The QMP must demonstrate the DCC's health and safety measures in relation to:
How they will achieve health and safety compliance How they will comply with the Health and Safety in Employment Act
1992 provisions with particular reference to Identifying work site hazards Developing emergency procedures to deal with work site
hazards Recording work site safety incidents and accidents.
Traffic management plans and procedures must be included in the QMP, particularly showing the DCC's plans in regard to:
COPTTM and/or the Local Roads Supplement.
5.2 Data Display
The DCC's QMP must show they have:
Some form of data display that allows the system outputs to be visually monitored in real time to ensure data is being collected and that it is valid
A computer screen that at minimum displays all processed outputs as a function of distance, along with recorded events.
5.3 Data Backup
The DCC's data backup systems will include:
Establishing and implementing data backup procedures which minimize data loss in the event of the theft of a vehicle or equipment, and taking responsibility for any such loss
DVD-RW or USB drive storage devices shall be used for storing both raw and processed data.
Data Collection Specification23
Specification for Road Condition Data Collection Services
5.4 On-going Validation
The DCC's QMP must include repeatability surveys to confirm the data are consistent, by showing they will:
Re-measure a segment of road every four weeks or so; the segment must be at least 10 km long, and have been surveyed at least 14 days previously
Supply these data to the Client within five to allow them to independently confirm the data are consistent.
It is recommended that when the DCC teams are near the validation sites they take advantage of the opportunity to revalidate the equipment. This can then be incorporated into the revalidation process described above.
At the end of the survey the DCC shall repeat their data collection on the validation sites to confirm that there have been no major changes in the equipment measurement process. This need not be a full revalidation exercise but must demonstrate the equipment's performance has not changed.
6 TRAFFIC MANAGEMENT AND SAFETY6.1 Health and Safety Compliance Notice
The DCC must demonstrate a responsible attitude towards occupational health and safety. They must ensure they comply with relevant work site safety laws and in particular the Health and Safety in Employment Act 1992.
The DCC must observe the provisions of the Health and Safety in Employment Act 1992, especially in relation to:
Identifying work site hazards Minimizing the effects of significant hazards where these cannot be
eliminated Providing appropriate protective measures Devising emergency procedures appropriate to the work Implementing a hazard identification and assessment process and
determining the effect each hazard has on employees.
Data Collection Specification24
Specification for Road Condition Data Collection Services
6.2 Traffic Management Plan
The DCC will be responsible for providing the traffic management services defined in a Traffic Management Plan (TMP); these services' purpose will be to minimize risks to DCC staff and other road users during the field survey operations.
The TMP will meet the requirements of COPTTM or the Local Roads Supplement <delete as applicable> and establish the minimum requirements for traffic management required for the field survey operations. The process is as follows:
The DCC will develop a generic TMP for the Client's approval. It will cover all aspects of the work (including calibration and validation and all other field operations), and include work hours, and details of non-working days (such as weekends and holidays).
The DCC will submit the TMP to the Client or Client representative for approval at least one week before the surveys start and equipment calibration and validation is undertaken.
It is the DCC's responsibility to take appropriate measures to keep all field operations, survey crew and other traffic safe at all times. The DCC shall also ensure that the data collection exercises cause minimum disruption/congestion. To achieve these requirements:
Survey vehicles shall travel as fast as practicable (up to the operating speed of the road), while taking into account safety and high quality data collection requirements
The DCC shall maintain a management and safety register for recording all incidents, accidents and comments/issues raised by the community.
7 DATA PROCESSING AND STORAGE7.1 Data Format
All data items are to be processed by the DCC and stored in the following formats:
Raw data – these are the individual measurements recorded by the equipment (e.g. the raw roughness counts must be provided in ASCII delimited format <Client to specify>. The raw data must contain sufficient data to enable reprocessing to obtain the processed data.
Processed data – this is raw data which has been processed and summarised at the specified reporting interval. The formats of the processed data must <Client to specify> be comma separated values and MS Excel.
The file format of the data items and mapping coordinate system shall be agreed with the client.
Data Collection Specification25
Specification for Road Condition Data Collection Services
7.2 Providing Data
The DCC is to provide the following data:
Calibration and validation – all data related to initial and post survey calibration and validation; this includes undertaking 10 km field validation within two weeks from the completion of the calibration and validation
On-going validation – the raw and processed data from the resurveyed section checks should be supplied within five calendar days of the re-survey
Survey data – complete raw and processed survey data shall be provided to Client within 30 days of the final links in the contract package being surveyed.
For each data item, the date of the survey has to be stored in the database file.
7.3 Data Review and Acceptance
When the Client or their representative receives the data from DCC, they must audit and verify the data. If the data audit reveals discrepancies or other problems the DCC shall take appropriate action to rectify the problem. This requirement includes undertaking work to correct the data processing routine or resurvey the road.
The Client will endeavour to review all data supplied and issue a Data Acceptance Certificate in less than 30/60 <delete as applicable> calendar days provided:
No discrepancy or issue is found with the supplied data
It has been successfully uploaded into the Client's RMS.
If a resurvey request is made because of a data discrepancy within 30 calendar days of the data being supplied no additional payment for the resurvey will be made. The only exception will be is if the DCC can show that any perceived data error was incorrect.
8 MONITORING AND REPORTING8.1 Initial Meeting
An initial meeting shall be held as soon as the staff are mobilised but before any field activity is initiated. This meeting will include at least the following activities:
Introducing DCC team members Providing a brief overview of the DCC's proposed work programme Finalising the survey and personnel schedules Familiarising the DCC with the Client's RMS and Client with the DCC's
Data Collection Specification26
Specification for Road Condition Data Collection Services
software Providing and overview of the QMP and TMP and their requirements.
8.2 Quality Management Plan
Report on quality control and assurance procedures adopted – refer to Section 5.11
8.3 Final Report
The final report shall include the overall summary of the project tasks including:
Details on calibration and validation Field surveys and data backup and archives taken Overall survey statistics including survey downtime Summarised presentation of the survey results covering the network
length and road condition Major problems and issues faced and the remedial measures taken Data statistics such as daily survey lengths, in terms of bar charts Lessons learnt and recommendation for future data collection contracts.
The annex to the draft final report shall include DVDs containing a complete set of all the survey data collected in the various formats specified in Section 3. An index shall be provided to assist in locating data on specific roads or within information categories.
T The DCC must submit a draft final report to the Client not more than 20 days after the survey work has been completed. It will then be revised and resubmitted after addressing the Client's comments on the final report.
The final report shall also include a separate Executive Summary about the project for distributing to wider audience. This will include, a brief overview of its activities, outputs and achievements.
9 KEY DELIVERABLES
Data Collection Specification27
Specification for Road Condition Data Collection Services
9.1 Deliverables
The following shall be submitted as per the schedule specified elsewhere in the document:
Manuals and Plans Traffic Management Plan Quality Management Plan.
Reports and Data Equipment calibration and validation Progress reports with interim raw and processed data Final report with final raw and processed data.
9.2 Format
All deliverables shall be submitted in both printed and electronic format except for the survey data. This must be submitted in electronic format unless otherwise specified.
Electronic copies of all documents and reports shall be provided in MS Word, Excel or other original source file format as appropriate to be agreed with the Client. Reports shall also be presented in PDF format.
9.3 Intellectual Property
All data, reports, plans, manuals, processes specific to the project and all documents or reports prepared or developed as part of the project shall be the Client's property; the Client will also own these documents' intellectual property. The DCC may make use of or refer to such documents for marketing and/or other project purposes after obtaining the Client's written consent.
At the end of the project, the DCC must return to the Client all the other documents; these include all the data, maps and reports the Client or other organisations have supplied to them to assist with the work.
10 SCHEDULE AND RESOURCES10.1 Project Schedule
It is anticipated that mobilisation will occur by: <insert date>
Commencement: <insert date>
Duration: <insert time/date>
10.2 Data Collection Contractor’s Personnel
The DCC is expected to have the following relevant experience:
<Add as required>.
Data Collection Specification28
Specification for Road Condition Data Collection Services
11 BASIS OF PAYMENT11.1 Basis of Payment
The road length provided in this TOR is only an estimate. The Client may increase or reduce the survey length according to the available budget. However, the DCC should plan on surveying a minimum of <Insert length> km of paved roads.
The project is to be treated as an output based contract and the DCC must prepare their proposal accordingly. To that end:
The DCC must procure all equipment required for the project The equipment shall not be turned over to the Client at the end of the
project <modify to suit>. Refer to Section 2.14. The payments will be paid on a zero-rated (survey completed for number of
km or stations) basis using the unit rates supplied Lump sum payments will be made after every milestone such as an
acceptance certificate There shall be no mobilisation and demobilisation payment.
The payment schedule shall be as follows.
Activity Payment Type
Basis
Acceptance for survey certificate
lump-sum 10%
Data collection pro rata per lane.km or per number
Data processing pro rata per lane.km or per number
Acceptance of final report lump-sum 15%
Per km (or lane/.km) or per number unit rates shall be used for additional network.
<modify to suit>
11.2 Payment
Invoices shall be submitted as per the payment schedule or at the end of every month <select as appropriate>. The respective time sheets for the key staff and the field staff must accompany all invoices. The Client will audit all invoices and all reasonable costs shall be paid within 10 <modify to suit> working days from the receipt of the invoice.
Data Collection Specification29
Specification for Road Condition Data Collection Services
The time spent by the staff shall be compared with the proposed time schedule agreed in the contract. The actual time spent by the staff on the project shall only ever be paid to the maximum of the agreed schedule in the contract. Any less time than that specified on the contract schedule shall be deducted from the final payment or any other intermittent payment <modify to suit>.
Data Collection Specification30