The building blocks of a geospatial assurance system.

Seven platform concepts that can be delivered independently or combined into a comprehensive asset intelligence system. Each is designed as a modular component with a clear data model.

Modular, linked and progressively deployable

Each concept can be started in isolation. The core data model is designed so that modules connect as they are added — there is no need to build everything at once.

Asset
Physical structure
Exams
Source evidence
Reviews
Engineering judgement
Risk / Sev
Review output
Recs
Actions
Evidence
Docs / photos
Audit
Decision history
Incidents
Events / strikes

Structures Assurance Platform

Prototype ready

A geospatial platform for bridges, culverts, tunnels, retaining walls and operational structures. Connects asset identity, location, examination history, engineering reviews, risk scores and recommendations into a single navigable system.

Built around a clear data model: Asset → Exams → Reviews → Recommendations → Evidence → Audit. Each layer is explicitly modelled and linked, so it is always possible to trace a risk score back to the examination evidence and engineering judgement that produced it.

Geospatial asset map with route and type filtering
Examination status and history per asset
Structural assessment status and capacity register
Risk and severity scoring with matrix
Recommendation lifecycle management
Evidence pack generation
Audit trail of all review decisions
climate and scour risk overlay (planned)
incident and bridge strike recording (planned)

Asset Review Workbench

Platform concept

A structured system for engineering reviews where reviewers assess examination evidence, photographs and documents, record risk and severity, and create recommendations. Designed to support — not constrain — engineering judgement.

The workbench is designed so that a reviewer sees the asset record, all linked examination evidence and any prior recommendations in a single interface. Risk decisions are recorded with the rationale, not just the score.

Evidence and photograph review panel
Structured risk and severity recording
Recommendation creation with categorisation
Review status tracking (draft, submitted, approved)
Multi-reviewer workflow with sign-off
Linked to asset, exam and evidence records
Exportable review outputs

Evidence Pack and Audit Trail System

Platform concept

A system for generating audit-ready evidence packs for individual assets, routes, regions or whole programmes. Designed to support regulatory review, internal audit and programme assurance.

Evidence packs are assembled on demand from the underlying data model — not manually compiled. This means they always reflect the current state of the record and can be regenerated if new information is added.

Asset identity and location reference
Full inspection and examination history
Assessment and review history with decisions
Risk decisions with rationale and timestamps
Recommendations with status and evidence
Linked photographs and documents
Mitigation records and next actions
Ownership and responsibility assignment
Complete audit trail of changes

Climate and Scour Risk Layer

Platform concept

A future geospatial overlay layer that adds environmental and climate risk context to the asset map. Designed to help prioritise inspection and intervention at assets with the highest environmental exposure.

Environmental risk context changes the prioritisation picture. An asset with a moderate structural risk score but located in a flood zone or adjacent to a known scour site may warrant earlier intervention than its structural score alone would suggest.

Flood zone proximity overlay
Watercourse proximity analysis
Known scour site locations
Drainage dependency mapping
Extreme rainfall exposure scoring
Historic flood and scour incident records
Weather alert integration (future)
Climate projection scenario overlays (future)

Incident and Bridge Strike Provision

Platform concept

A future-ready data model for recording bridge strikes, flood and scour events, structural damage reports and emergency inspections. Designed to connect incident records back to asset and examination history.

This module does not need to be customer-facing initially. It can begin as an internal recording and tracking system, with the map and dashboard views added once the data model is established and populated.

Bridge strike recording and classification
Flood and scour event records
Structural damage report creation
Emergency inspection triggering and tracking
Incident-to-asset linkage
Timeline of incidents per asset
Management summary and route-level reporting

Baseline-to-Current Assurance

Platform concept

Using historic review baselines — such as DER-style reviews — to compare what was flagged historically with what has changed. Enables structured assurance that historical recommendations have been acted on and that risks have been managed.

The key questions this answers: Which historical recommendations were completed? Which assets remain at high risk? Which risks have been demonstrably reduced? Which evidence is missing? Which assets need a current-state review? These questions are hard to answer from static records alone.

Historic baseline import and mapping
Recommendation completion tracking since baseline
Assets remaining at historic high risk
Risk reduction evidence per asset
Missing evidence identification
Assets requiring current-state review
Baseline-to-current comparison dashboard

AI / Analytics Layer

Platform concept

Careful, targeted use of AI to support engineering analysis — not to replace engineering judgement. AI assistance is used to accelerate repetitive analytical tasks and surface patterns that are difficult to detect manually.

All AI outputs are presented as suggestions for review, not as decisions. The system flags, clusters and summarises — the engineer decides. This matters particularly in safety-critical contexts where the reasoning behind a risk decision must be defensible and human-authored.

Long recommendation description summarisation
Similar defect clustering and grouping
Duplicate recommendation detection
Inconsistent risk rating identification
Assets with profiles similar to past failures
Assets predicted to become overdue
Regulator-ready structured summary generation

Start with the data. Build toward intelligence.

A full platform does not need to be built in one go. Most successful implementations start with the data model and a working prototype of the core asset map, then add modules as requirements are confirmed and data is validated.

The architecture is designed so that modules can be added progressively without reworking what has already been built. A common data model and API layer means that a new module connects to the same underlying records.

The AI and analytics layer is always the last thing added — only once the data is clean, the model is stable and the team understands what they have.

Discuss a platform concept

Interested in one or more of these concepts for your organisation? Discuss how it could be adapted to your existing data, systems and operational context.