Watch the overview
76 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00A concrete-pavement assessment connects a kilometre interval
- 0:03to surface type, observations and condition indices.
- 0:07If that interval is wrong, a correctly
- 0:09typed rating can still be attributed to
- 0:11the wrong section. The implemented concrete segment
- 0:15check uses a zero point two kilometre
- 0:17baseline and a fifty-percent band. In this
- 0:20example, zero point one five kilometres falls
- 0:23within the band. A zero point four
- 0:25kilometre segment is outside the zero point
- 0:28one to zero point three band and
- 0:30produces a warning. A reversed interval is
- 0:33handled separately; these are not the same
- 0:35issue. The concrete template also declares allowed
- 0:38surface-type codes. An unrecognised code is a
- 0:41schema finding. Keep the original schema version
- 0:44and field positions when correcting it. Condition-index
- 0:48fields outside zero to one hundred are
- 0:50errors where those fields are present. Field
- 0:53types, declared rating ranges and index bounds
- 0:56provide different pieces of evidence. Compare the
- 0:59finding with the actual assessed section and
- 1:01survey notes. The system does not infer
- 1:04concrete performance from a tidy file. Correct
- 1:07attribution or coding only when the evidence
- 1:09supports it, then rerun.
A concrete record has a location
A concrete-pavement assessment connects a kilometre interval to surface type, observations and condition indices. If that interval is wrong, a correctly typed rating can still be attributed to the wrong section.
The implemented concrete segment check uses a zero point two kilometre baseline and a fifty-percent band. In this example, zero point one five kilometres falls within the band.
Recognise the warning
A zero point four kilometre segment is outside the zero point one to zero point three band and produces a warning. A reversed interval is handled separately; these are not the same issue.
The concrete template also declares allowed surface-type codes. An unrecognised code is a schema finding. Keep the original schema version and field positions when correcting it.
Separate interval integrity from pavement condition
In a fictional concrete-pavement extract, 0.000–0.150 km and 0.000–0.400 km produce different length-review outcomes under the implemented 0.2 km baseline and its 50% band. Those examples explain a rule boundary; they do not establish which segmentation a contract requires.
Keep the slab or distress coding, assessment interval and network location together. Review an unexpected interval against the survey plan before splitting or shortening records. A record can satisfy field-domain checks while still needing engineering judgement about the observation it represents.
Separate index and field checks
Condition-index fields outside zero to one hundred are errors where those fields are present. Field types, declared rating ranges and index bounds provide different pieces of evidence.
Compare the finding with the actual assessed section and survey notes. The system does not infer concrete performance from a tidy file. Correct attribution or coding only when the evidence supports it, then rerun.
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.