Why it matters
Without this system, unnoticed shoreline and riverbank shifts risk damage to significance, failed consents, disrupted access, lost grants, and ineffective rescue recording when events occur.
From design to safety
Design
Significance-based risk modeling
The system ingests shoreline maps, tidal data, sediment samples, and conservation management plans to model erosion pathways and propose protection measures aligned with significance.
- sea cliff toe collapse section
- riverbank revetment stones
- historic sea wall stone blocks
- tidal gauge monument
Build
Intervention planning and installation
It assesses quinquennial inspection defects, repair feasibility, and service integrations to guide minimal intervention and adaptive reinforcement.
- sea cliff toe collapse section
- riverbank revetment stones
- historic sea wall stone blocks
- tidal gauge monument
Operation
Real-time monitoring and alerts
Sensors collect ground movement, water level, rainfall, and surface wetness to issue alerts and update risk maps for ongoing site management.
- sea cliff toe collapse section
- riverbank revetment stones
- historic sea wall stone blocks
- tidal gauge monument
Maintenance
Cyclical inspection data integration
The AI consolidates quinquennial inspection notes, sensor readings, and condition surveys to forecast maintenance windows and materials needed.
- sea cliff toe collapse section
- riverbank revetment stones
- historic sea wall stone blocks
- tidal gauge monument
Safety
Emergency response and safeguarding
It triggers safety shutoffs, evacuation routes, and protective actions while recording incident data for post-event review and consent compliance.
- sea cliff toe collapse section
- riverbank revetment stones
- historic sea wall stone blocks
- tidal gauge monument
Part by part
- 1
sea cliff toe collapse section
- Watch for
- Creeping shoreline retreat, ground fissures, and talus block detachment near the cliff base.
- AI action
- Reads shoreline change rates and triggers protection alerts to site manager.
- 2
riverbank revetment stones
- Watch for
- Loss of stone facing, undercutting of gabions, or void formation behind revetments.
- AI action
- Monitors pore pressure, displacement, and surface cracking; issues maintenance tickets.
- 3
historic sea wall stone blocks
- Watch for
- Dislocation of blocks, mortar degradation, and displacement under storm surge.
- AI action
- Analyzes lidar profiles and mortar condition to schedule repointing and re-setting.
- 4
tidal gauge monument
- Watch for
- Rising water levels, surge events, long-term sea level indicators.
- AI action
- Feeds tide height trends into risk map and triggers evacuation or protective barriers.
- 5
rescue recording log at field station
- Watch for
- Gaps in rescue documentation after events, loss of photographic records, incomplete metadata.
- AI action
- Flags missing records and prompts field teams to complete data capture.
- 6
drift and sediment monitoring beacon
- Watch for
- Sudden sediment shifts, slumping, or new scour channels.
- AI action
- Sends real-time shifts alerts and maps sediment movement.
Worked example
Catching a cliff retreat before a breach
Illustrative scenario with sample data.
A coastal ruin face shows increasing fissuring; tidal data indicate higher frequency surges and sediment loss near the base.
Signal in
site_id: WL-07, age: 780, yearly_visitors: 12000, shoreline_distance: 28.4m, tilt_rate: 0.3mm/day, rainfall_last_30d: 180mm
System out
alert: cliff_retreat_risk; action: schedule baseline survey; monitor_wave_runup; restrict access to toe area; update conservation management plan.
Human sign-off: Conservation architect reviews risk map, approves protection measures, and submits amendment to planning authority.
How to roll it out
Phase 1
Weeks 1 to 4: Baseline
Establish data pipelines, calibrate sensors, and set initial risk thresholds across coastal and river sections.
Phase 2
Weeks 5 to 12: Deployment
Install monitoring beacons, integrate existing quinquennial records, and begin real-time data feeding into risk maps.
Phase 3
Months 4 to 6: Operational
Run alerts in simulated events, refine response protocols, and train site staff and guardians on workflows.
Where people stay in charge
- Decisions about interventions and safety actions must be signed by the conservation architect and site manager.
- Changes to the conservation management plan or consents must be approved by the heritage consenting authority.
- Data collection, storage, and preservation decisions must be overseen by the designated records officer with approval from the trustees.
Questions owners and crews ask
What data feeds drive erosion monitoring at heritage sites?
The system reads shoreline maps, lidar or photogrammetry surveys, tidal and surge data, rainfall, soil moisture, and sediment movement records to generate risk assessments and trigger actions.
Who approves structural interventions indicated by AI alerts?
Conservation architect signs off on intervention plans; site manager coordinates with the curator and, if needed, the heritage consenting authority before works commence.
How are safety decisions validated for visitors?
Safety officers review AI-suggested actions against risk assessments, and the trustees sign off on any route closures or evacuation plans.
How is records integrity maintained for rescue operations?
A records officer ensures rescue logbooks and metadata are complete, stored securely, and linked to the conservation management plan for audit trails.