Watch the overview
81 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00A falling weight deflectometer record describes a
- 0:03test at a survey point. Treating it
- 0:05like a start-and-end road segment can produce
- 0:08the wrong explanation and the wrong expectations.
- 0:12The F W D template uses survey
- 0:14kilometre together with road, lane, date, drop
- 0:17number, load and deflection fields. Keep that
- 0:21test context together when preparing and reviewing
- 0:23the export. For example, a word entered
- 0:27in an integer deflection field is a
- 0:29type error. Missing required values and disallowed
- 0:32declared codes are different findings, each with
- 0:35a specific correction. Declared decimal precision can
- 0:39produce warnings. Preserve the instrument units and
- 0:42original export; a field passing a numeric
- 0:45check does not prove that the physical
- 0:47units or calibration are correct. Where project
- 0:50references support it, the survey point can
- 0:52be compared with the network extent and
- 0:54road geometry. Point-location checks are different from
- 0:58segment-length checks. The illustrated deflection profile is
- 1:02explanatory, not a computed pavement design. Do
- 1:05not read schema conformance as a certified
- 1:08basin shape, instrument calibration or guaranteed structural
- 1:12capacity. Review the source and the applicable
- 1:15findings.
A test point is not a segment
A falling weight deflectometer record describes a test at a survey point. Treating it like a start-and-end road segment can produce the wrong explanation and the wrong expectations.
The F W D template uses survey kilometre together with road, lane, date, drop number, load and deflection fields. Keep that test context together when preparing and reviewing the export.
Check the declared field types
For example, a word entered in an integer deflection field is a type error. Missing required values and disallowed declared codes are different findings, each with a specific correction.
Declared decimal precision can produce warnings. Preserve the instrument units and original export; a field passing a numeric check does not prove that the physical units or calibration are correct.
Keep a drop attached to its station
Review a fictional drop by keeping its road, lane, survey kilometre, date, load and sensor values together. If a deflection field expects an integer and contains a word, investigate that type error separately from a coordinate mismatch. Neither finding gives the reviewer permission to invent a replacement measurement.
A profile illustration helps explain sensor context, but it is not a computed pavement design. Check instrument units and supporting calibration evidence through the appropriate engineering process. Numeric acceptance of a field cannot establish structural capacity or confirm that the sensor was correctly calibrated.
Place the point on the network
Where project references support it, the survey point can be compared with the network extent and road geometry. Point-location checks are different from segment-length checks.
The illustrated deflection profile is explanatory, not a computed pavement design. Do not read schema conformance as a certified basin shape, instrument calibration or guaranteed structural capacity. Review the source and the applicable findings.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.
Put it into practice
Review check templatesSign-in and the relevant account permissions are required.