HROUS

FWD Testing Quotes for Australian Road Managers: Requirements

Advertisement

For comparable falling weight deflectometer (FWD) testing quotes, give every bidder the same route, test-location schedule, field conditions and measurement deliverables. Separate applicable specification requirements from your contract inclusions and optional engineering interpretation.

Advertisement
Female engineer stands in anechoic chamber with a car for sound testing.
  • Applicable requirements: identify the measurement procedure and survey specification the contract requires bidders to follow. Austroads publishes an FWD procedure and a network-level specification. [1][2]
  • Recommended contract inclusions: define route coverage, measurement fields, access responsibilities, missed-station treatment and file handover.
  • Separately priced options: itemise structural indices, layer-modulus back-analysis and rehabilitation interpretation rather than accepting an undefined “survey report”. These are distinct from basic measurement data. [3][4]
Advertisement

Define the investigation and issue one route brief

FWD testing measures pavement deflection response to load. Queensland’s Department of Transport and Main Roads (TMR) says it is commonly undertaken before destructive investigation to identify homogeneous sections with different structural responses and help target further investigation. [1][3]

Build the route brief around these TMR scope inputs:

  • Investigation purpose: state the decision the survey must support and describe the proposed works. [3]
  • Route boundaries: identify each road and section, with start and finish chainages or clearly identifiable physical features. [3]
  • Design and traffic context: include relevant design life, reliability, traffic volumes and expected heavy-vehicle growth. [3]
  • Timing: state the delivery timeframe and relevant project constraints. [3]
  • Site conditions: describe known geometry, drainage and flooding risks, utilities, environmental constraints and traffic-management considerations. [3]
Advertisement

Attach available construction or as-constructed drawings, condition and maintenance records, previous investigation results and relevant local knowledge. TMR recommends reviewing existing information before onsite work, but warns that road database records need onsite verification because errors exist. [3]

Keep the guidance hierarchy clear. Austroads’ AGAM-T006-11 defines the FWD measurement procedure; AGAM-S002-08 covers minimum equipment, calibration, validation and survey-method requirements for network-level testing. Their publication summaries do not reproduce the detailed requirements, so use the documents themselves when specifying compliance. [1][2] TMR’s investigation guidance is Queensland-specific, not a nationwide tender requirement. [3]

Advertisement

Set lanes, wheel tracks and test locations

Label the investigation network-level or project-level. The December 2012 New Zealand guide, Collection and Interpretation of Pavement Structural Parameters using Deflection Testing, distinguishes wider-spaced network assessment from closer-spaced project assessment with deeper scrutiny and analysis. It is background guidance, not an Australian requirement. [4]

Give every bidder the same test-location schedule. Specify for each section:

  • Direction of travel, lane and wheel track. [4]
  • Station spacing and intended station count. [4]
  • Additional targeted locations, listed separately from regular spacing. [3][4]
  • Planned variations in coverage, so bidders price the same schedule. [3][4]
Advertisement

For illustration, the New Zealand guide describes standard project-level testing in the left wheeltrack, with a minimum of 30 tests and spacings down to a minimum of 10 m for short roads. [4] This is not an established Australian default. [4] The Austroads specification summary does not state numerical spacing or location tolerances; identify the applicable requirements and settle the project’s sampling schedule in the brief. [2]

Choose locations to answer the investigation question, not simply to achieve regular spacing. TMR recommends reviewing project scope and available desktop, visual and non-destructive investigation information to identify representative or homogeneous sections and guide further investigation. [3]

Advertisement

Specify measurement fields and field conditions

Use the following as a recommended procurement schedule, with explicit units and field definitions—not as an Australian statutory minimum. The New Zealand guide provides background for location, sensor readings, loading and temperature records. [4]

  • Route and station identity: define route identifiers, station numbering and chainage convention. Require each reading to link to its route, station and actual chainage or location. [4][5]
  • Direction, lane and wheel track: define consistent labels and require the actual test position for each station. [4]
  • Spatial reference: nominate the coordinate reference and its relationship to chainage. Require coordinates and the positioning method. NTRO describes differential-GPS and distance-measurement referencing tied to road chainage and network location; this is a provider example, not a mandatory method or accuracy threshold. [5]
  • Sensor configuration and offsets: require bidders to declare sensor identifiers, offsets from the load and reporting arrangement, and retain that configuration with the readings. Pavement Management Services describes geophones measuring deflection under a known load. [4][6]
  • Individual sensor deflections: specify units and require each sensor’s peak deflection. Distinguish measured readings from subsequently normalised values. [4]
  • Applied load or load-cell pressure: define the reported quantity and units, and associate each recorded load or peak pressure with its corresponding deflections. [4][6]
  • Temperatures: define which temperatures are recorded and their units, with labelled values linked to each test point. [4]

Keep field observations separate from measurement columns. Request relevant surface condition, distress location and severity, drainage and access constraints where they affect the investigation; TMR identifies these matters in its visual-investigation guidance. [3]

Advertisement

Price access and missed-station treatment

TMR identifies traffic management, utilities and environmental constraints as inputs when defining an investigation’s scope. [3] Allocate these responsibilities in the brief:

  • Traffic management: who arranges and provides it, and whose price includes it.
  • Access coordination: who coordinates access to each section and advises the testing crew of restrictions.
  • Work windows: agreed testing periods and how changes or cancellations will be handled.
  • Known constraints: who provides information about services, environmental restrictions and operational limitations.

Request separate pricing lines—or explicit inclusions—for mobilisation, traffic management and return visits. The New Zealand guide gives testing costs ranging from $10 per test point for large surveys requiring minimal traffic control or mobilisation to over $15 per point, and from $25 to over $100 per lane-km for FWD. These are not current Australian price benchmarks. [4]

Advertisement

Write missed-station clauses as contract decisions. The cited Australian publication summaries and TMR guidance do not establish a missed-station definition, substitution tolerance, retest obligation or omission-payment rule. [1][2][3] Recommended clauses should:

  • Identify each omitted station and record why it could not be tested.
  • Record the actual location of a replacement test against the planned station.
  • Require agreement before substituting a location beyond the project’s stated tolerance.
  • Allocate responsibility and charges for return visits, including where access was unavailable.
  • Define payment treatment for omitted, substituted and subsequently completed stations.

Separate measurements from engineering interpretation

Make measured deflection data and agreed collection-quality records the base survey deliverable. List processing and engineering interpretation as separately priced options unless the project requires them in the base scope. This is a procurement recommendation, not a mandatory Australian pricing model.

Advertisement
  • Measured data—base price: require each sensor’s measured response with the agreed location, load, temperature and sensor-offset information, plus specified collection-quality records. The New Zealand guide distinguishes basic test-point data from analysis products. [4]
  • Processed or normalised structural indices—separate option: identify the requested indices and normalisation basis. The guide describes load-standardised central deflection and curvature as processed parameters; retain the individual measured readings alongside them. [4]
  • Layer-modulus back-analysis—separate option: define modelling inputs and outputs. TMR says FWD data can be back-analysed to help determine pavement-layer moduli for mechanistic design using CIRCLY. Pavement Management Services also describes software-based analysis of modelled layer properties. [3][6]
  • Rehabilitation interpretation or pavement design—separate option: specify whether the deliverable is preliminary treatment options or pavement design. The New Zealand guide includes nominal rehabilitation options in project-level reporting; TMR places investigation within a broader pavement-design process. [3][4]

The New Zealand guide bundles basic data, structural indices and preliminary mechanistic analysis differently for network and project reporting. Those packages illustrate why inclusions need unpacking; they do not define Australian contractual requirements. [4] For each interpretation product, list assumptions, client-supplied inputs, outputs and exclusions.

Advertisement

Check files before authorising interpretation

Request an example file layout and data dictionary with each proposal. Specify a usable tabular measurement export and whether native instrument files must also be delivered. Treat formats, naming conventions, coordinate reference systems and native-file access as contract choices, not established Australian requirements.

The New Zealand guide illustrates a handover containing location, each deflector’s peak reading, peak load-cell pressure and temperatures, alongside the processed structural number parameter SNP. Its RAMM spreadsheet context is an example, not an Australian format requirement. [4]

Make these checks a contractual checkpoint before optional back-analysis:

Advertisement
  • Coverage: reconcile planned and delivered stations, identifying omissions and substitutions.
  • Location: check route, chainage and spatial references agree. NTRO’s published approach links differential-GPS and distance measurements to chainage and network location. [5]
  • Measurements: confirm individual sensor deflections and offsets, load and temperature fields—not just summary results. [4][6]
  • Processing: distinguish measured columns from calculated indices and modelled layer moduli. [4]

Agree how missing, rejected or unusable records will be identified and resolved. Set review timing in the contract rather than assuming an official acceptance deadline or universal rejection thresholds.

Compare bids against the issued scope

For each item, record the client-specified scope, bidder response, price inclusion, exclusion or departure, and clarification required:

  • Investigation purpose, road sections, chainages and available records.
  • Lanes, wheel tracks, station spacing and targeted locations.
  • Sensor readings, offsets, load, temperatures and spatial reference.
  • Field conditions, traffic management and access responsibilities.
  • Omissions, substitutions, return visits and payment treatment.
  • File formats, required fields and handover checks.
  • Separately priced processing, back-analysis and rehabilitation interpretation.

Resolve qualifications before comparing totals. Where coverage, outputs, access assumptions or interpretation still differ, seek aligned offers rather than treating the quoted totals as equivalent.

References

  1. Pavement Deflection Measurement with a Falling Weight Deflectometer (FWD) (austroads.gov.au)
  2. Specification for Pavement Deflection Measurement with a Falling Weight Deflectometer (FWD) (austroads.gov.au)
  3. Guideline Pavement Investigation and Analysis July 2024 (qld.gov.au)
  4. Collection and Interpretation of Pavement Structural Parameters using (squarespace.com)
  5. FWD/HWD | Heavy Falling Weight Deflectometer | NTRO (ntro.org.au)
  6. Heavy/Falling Weight Deflectometer — Pavement Management Services (pavement.com.au)
Advertisement

Similar reads