Application Overview
What Road Maintenance models, and the ideas behind it
Three Layers
| Layer | What it holds | Models |
|---|---|---|
| Network register | Where work happens | District, Network, Road, Road Section, Road Location |
| Reference library | The rules of the guideline | Defect Type, Defect Sub Type, Corporate Priority, Road Category, Intervention Rule, Maintenance Element, Maintenance Activity, Activity Standard, Valid Defect Activity, Unit Of Measurement |
| Operational records | The work itself | Inspection, Defect Observation, Defect Assessment, Defect Log Entry, Defect Backlog, Planned Work, Work Order, Work Execution, Completion Inspection, Defect Closure |
Defect Classification
- Defect Type — two-character codes: PH Pothole, CR Cracking, ED Edge Break, GD Guardrail Damage, and so on.
- Defect Sub Type — four-character measurable subdivisions: PH01 is a pothole under 300 mm diameter, PH02 is 300 mm or larger.
Corporate Priorities
| # | Code | Name | Behaviour |
|---|---|---|---|
| 1 | HAZ | Hazard | Mandatory action — field weighting not applied |
| 2 | ORD | Ordered Works / Special | Mandatory action — field weighting not applied |
| 3 | SAF | Safety | Scored: corporate × field weighting |
| 4 | LEG | Legislative | Scored |
| 5 | PRE | Preventative | Scored |
| 6 | APP | Appearance / Usability | Scored |
Intervention Rules (IL/RT)
The central design decision: intervention levels and response times are not stored on the defect type. They vary by defect sub-type × road category × corporate priority, so each combination is one Intervention Rule record holding the initial and upper intervention levels, the response time, and the weightings. Example from the demo data: a large pothole (PH02) requires a 2-day response on a Category 1 highway but 7 days on a Category 3 feeder road.
Priority score = corporate weighting × field weighting.
The Defect Lifecycle
Observed → Assessed → Logged → Planned → WorkOrdered → InProgress
→ Completed → Verified → Closed
(or → Monitoring, when below the intervention level)
(or → Backlog, when not rectified within the work cycle)
The defect log holds defects that reached the initial intervention level. The backlog holds logged defects not fixed within the cycle — each with a reason, review date and target date, because backlog defects deteriorate and must be reassessed.
Repair Choice
A defect maps to several permitted repairs, not one. The Valid Defect Activity table lists each option flagged preferred / temporary / permanent / emergency-only — e.g. a large pothole can be heavy-patched (permanent, preferred) or coldmix-filled (temporary make-safe), and the demo data uses both on the same defect.