Arbrium — infrastructure asset intelligence

Data exchange · Arbrium Connect

Structured information in. Better information out.

Arbrium Connect is the layer between your source systems and Arbrium's intelligence — how authorised infrastructure data comes in, keeps its identity and provenance, and leaves again improved.

Request a demo Data quality & provenance
Data sources
Asset systemsSupplier dataField teamsGISInspection technology
Files today
ArbriumConnected infrastructure intelligence
Arbrium Connect

How information enters and leaves — identity and provenance kept.

Connected asset graph

Assets, inspections, projects and works — and how they relate.

Relational intelligence
RelationshipsDependenciesData qualityCoordination
Exports today
Client environment
GISEngineeringReportingAPIsPlannedExisting systems

The model

Arbrium doesn't need to own every asset record.

It needs to understand the relationships between them.

Authoritative data can stay where it's mastered today. Arbrium represents it consistently, relates it to everything else on the network, and hands useful, structured information back.

  1. 01Source systemsWhere authoritative infrastructure data originates — asset systems, GIS, suppliers and inspection technology.
  2. 02Arbrium ConnectHow data enters and leaves Arbrium.
  3. 03Connected asset modelHow Arbrium represents authorised assets consistently, whatever their source.
  4. 04Connected asset graphHow assets, projects, inspections and works relate.
  5. 05Relational intelligenceHow Arbrium identifies potential relationships, dependencies and coordination opportunities.
  6. 06Existing client systemsWhere information continues to be managed and used.

Many sources

Not every team has to use the same system.

Arbrium doesn't require every organisation or contractor to capture data in Arbrium first. Information can come from the systems and suppliers that already hold it.

These are kinds of source, not named integrations. Connections to a client's own systems are scoped with each client.

  • GIS layers and asset registers as files

    GeoJSON, KML and Shapefile, zipped or loose; British National Grid converted.

    Available

  • Field teams

    Arbrium's survey app, with rapid capture of missing assets.

    Available

  • Contractor and supplier data

    Supplied as files and kept against the supplier and import.

    Available

  • Drones — Arbrium Air

    In beta

  • CSV and XLSX registers

    Planned

  • LiDAR-derived datasets

    Planned

  • API connections to asset and GIS systems

    Planned

  • Vehicle-mounted inspection, robotics and sensors

    Planned

  • Third-party inspection platforms

    Planned

What Connect does

Identity, provenance and exchange.

What's available today, and what's on the way. The architecture is designed for all of it; we only list as available what you can use now.

  • File ingestion

    GeoJSON, KML and Shapefile, with coordinate conversion.

    Available

  • External asset identity

    Your references and full supplied attribute set stay with each asset, from import to export.

    Available

  • Provenance

    Supplied values kept; every change attributed and dated.

    Available

  • Exports in your standards

    British National Grid Shapefile, GeoJSON, CSV and Excel, photo packs, PDF reports.

    Available

  • AI assistant access (MCP)

    Read-only, per-user and permission-aware.

    Available

  • Schema mapping

    Map a client's attributes to Arbrium fields at import.

    Planned

  • API connections

    Planned

  • Synchronisation and scheduled sync

    Planned

  • Change detection and conflict handling

    Planned

  • Approved data exchange

    Supplier proposes, asset owner approves, then it's exchanged.

    Planned

  • Webhooks and events

    Planned

In both directions

From your system, back to your system — better.

The platform is designed for information to flow both ways. One asset, followed round the loop:
  1. 01

    Client system

    Asset T-882, known location, existing attributes

  2. 02

    Arbrium

    Received with its reference and source kept

  3. 03

    Field / project activity

    Corrected location, updated condition, new evidence

  4. 04

    Data improvement

    Original value kept; who, when and why recorded

  5. 05

    Relational analysis

    Related assets and potential dependencies found

  6. 06

    Approved change

    Reviewed before it becomes the record

  7. 07

    Client system

    Improved information returned

Today the return journey is an export in your formats, which your team applies. Review-and-approve and direct write-back are planned — and Arbrium will not overwrite an authoritative system without approval.

Living intelligence

When the infrastructure changes, the intelligence can change with it.

A connected source will change. When an asset mastered elsewhere changes, Arbrium is designed to work out only what that change affects — not re-run everything.
  1. 01Detect the changed asset in a connected systemPlanned
  2. 02Synchronise the information that mattersPlanned
  3. 03Preserve provenance — what changed, where from, whenAvailable
  4. 04Identify which relationships may be affectedAvailable
  5. 05Re-evaluate just that part of the connected asset graphAvailable
  6. 06Surface new or changed dependencies and coordination opportunitiesAvailable

Steps 3–6 already run when an asset or a piece of work changes inside Arbrium. Doing the same for data mastered in other systems is planned.

Connected asset data

Bring information together from any source.

Data quality & provenance

Where every value came from.

Relational asset intelligence

What your assets affect.

Tell us what your systems hold. We'll show how it connects.

Request a demo Talk to our team