Connected asset data
Better infrastructure data, in both directions.
You supply the asset data you already hold. Arbrium makes it operational, field teams validate it, and an improved record — with every change traceable — goes back to your systems.
The data loop
Turn every inspection into an opportunity to improve the asset record.
CLIENT DATA
What you supply
- Asset IDs and your references
- Known coordinates
- Existing attributes
- The inspection requirement
ARBRIUM
Made operational
- Loaded to the map as it is
- Coordinate systems converted
- Assigned to surveys and teams
IN THE FIELD
Validated
- Positions corrected
- Attributes and condition updated
- Missing assets captured
- Assets no longer present marked
IMPROVED RECORD
With provenance
- Original values kept
- Who changed what, when
- Evidence attached
CLIENT SYSTEM
Returned to you
- Your references kept
- British National Grid Shapefile, GeoJSON, CSV, Excel
- Photos indexed to each asset
Better data out than came in
What happens to your register in the field.
Confirmed
Inspected and recorded against your own asset reference.
Corrected
Positions and attributes fixed on site. The original value, who changed it and when are kept.
Found in the field
Assets missing from the register captured on site and flagged as additional.
Not present
Assets that no longer exist are marked — kept in the record, out of the outstanding work.
Grouped
Individual trees brought together into a belt when that's how they're managed.
Evidenced
Photographs attached to the specific inspection, surveyor and date.
Provenance
Every value has a history.
When a surveyor moves an asset or corrects an attribute, Arbrium records the field, the value you supplied, the new value, who made the change and when. Imported attributes are kept exactly as supplied alongside the working record, and your own references stay attached from import to export.
Planned next: a review stage, so a supplier can propose a correction with evidence and the asset owner accepts it before it becomes the current value.
ASSET CHANGES · EXAMPLE
Tree T-A006
- Position53.7102, -1.9281 → 53.7104, -1.9277Surveyor · 14 Sep
- SpeciesAsh → Ash (multi-stem)Surveyor · 14 Sep
- Road reference— → A629Filled from location · 14 Sep
Exchange
Your data shouldn't end in Arbrium.
- Available
Import GeoJSON, KML and Shapefile
Zipped or loose files; British National Grid converted automatically.
- Available
Your references and attributes kept
Client IDs and the full supplied attribute set stay with each asset.
- Available
Field-level audit history
Original value, new value, who and when — for every correction.
- Available
Exports in your standards
British National Grid Shapefile, GeoJSON, CSV and Excel with lat/long and easting/northing, photo packs, PDF reports.
- Available
AI assistant access (MCP)
Read-only, per-user and permission-aware connection for tools such as Claude and ChatGPT.
- Planned
Correction review and approval
Supplier proposes, asset owner accepts, with evidence attached.
- Planned
Field mapping for client schemas
Map any supplied attribute to Arbrium fields at import.
- Planned
REST API and webhooks
- Planned
Scheduled synchronisation with client systems