Asset Vault

Your register says the sign is there.

Asset Vault drives the corridor and checks — every asset, every pass, with the photograph that proves it and a record of who decided what.

Video-survey verification Chainage-accurate referencing Audited end to end

The problem

A register drifts the day it is written.

Signs are hit and replaced by a contractor who tells nobody. Delineators disappear a few at a time. Then an audit arrives, or a claim, or a budget has to be defended — and the honest answer to “what is actually out there?” is that nobody has looked.

How it works · four records, kept separate on purpose

Evidence

Every finding carries the frame it came from.

A carriageway recorded by a survey vehicle, with guardrail, lighting columns and lane markings visible; a roadside billboard is automatically blurred.
Survey footage as Asset Vault stores it. Redaction runs before upload — and when it cannot run, nothing is uploaded rather than something unblurred.
  • Unpriced is not zero. Assets with no replacement rate are reported as unpriced and left out of the forecast, never counted as free.
  • A single miss is not a theft. A sign is called missing only after consecutive passes miss it — the threshold is yours.
  • Uncertainty is surfaced. A weak match is raised as “needs a human”; a badly configured survey is flagged, not reported as fact.
  • Nothing is deleted quietly. Assets are decommissioned with a date and a reason, and deletions show you what goes before you commit.

What you get

The whole operating loop, not just the inventory.

Asset register

Classification as data — add an attribute without a migration. Bulk edit gated by approval.

Linear referencing

Posted chainage with calibration points, so ch. 212+400 means what the boards say.

Video-survey verification

Capture, detect, triangulate, reconcile, review — store-and-forward, so no signal is a delay, not a lost survey.

Work management

Findings become work orders, dispatched by WhatsApp or SMS, closed with a photograph of the repair.

Planned maintenance

Cyclic regimes per class and corridor, with compliance measured against the plan — missed visits included.

Replacement forecasting

Ageing curves fitted from your own surveys, and a budget planner that chooses by consequence, not date order.

Concession compliance

Periodic returns computed from the register, checked by a second person, archived as issued.

Governance

Approval thresholds, four-eyes on large changes, escalation, and an audit trail that records refusals too.

Documents

As-builts, manuals, certificates and warranties held against the asset, with lapsed ones called out.

Deployment

Where your data has to live — hosted, on-premise or air-gapped. Licensing verifies offline against a signed key, so a disconnected site is supported, not a redesign.

Start with one video survey — a forward-facing camera and a GPS log in CSV, GPX or NMEA. Upload the drive through the browser; the server does the rest.

Scale when the corridor justifies it — move to a calibrated rig, add crews, set a maintenance regime per class.