Asset Vault
Asset Vault drives the corridor and checks — every asset, every pass, with the photograph that proves it and a record of who decided what.
The problem
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
Frames positioned, faces and plates blurred before anything leaves the vehicle.
Sightings matched to the register by position and class, correcting for the survey’s own systematic error.
Nothing changes until somebody agrees it. Every accept and reject carries their name.
The asset moves, is marked missing, or is enrolled — evidence still attached.
Evidence
What you get
Classification as data — add an attribute without a migration. Bulk edit gated by approval.
Posted chainage with calibration points, so ch. 212+400 means what the boards say.
Capture, detect, triangulate, reconcile, review — store-and-forward, so no signal is a delay, not a lost survey.
Findings become work orders, dispatched by WhatsApp or SMS, closed with a photograph of the repair.
Cyclic regimes per class and corridor, with compliance measured against the plan — missed visits included.
Ageing curves fitted from your own surveys, and a budget planner that chooses by consequence, not date order.
Periodic returns computed from the register, checked by a second person, archived as issued.
Approval thresholds, four-eyes on large changes, escalation, and an audit trail that records refusals too.
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.
Next
Drive one corridor. Compare it with your register.
A single video survey shows the gap between what is recorded and what is there. That first number is usually the whole business case.