Relational asset intelligence
See the relationships your asset register misses.
Connect assets, projects, inspections and planned works to understand what changes elsewhere when something changes here.
An example
Different assets. Different teams. Different projects. One connected delivery picture.
PROJECT
Vegetation programme
Surveyed by the vegetation team
Tree
Tree T-882
Recommended: Fell
Tree
Tree T-883
Recommended: Fell
must be done before
1.7m apart · felling sits inside the fence's work zone · different project
Confirmed by a personPROJECT
Boundary renewal
Delivered by the boundary contractor
Boundary fence
Fence F-104
Recommended: Replace
Coordination opportunity
3 planned interventions within 250m — review for shared access and traffic management.
One asset, many connections
The asset stays at the centre.
Trees and fences are the example, not the limit. Relationships run between any assets, inspections, projects and pieces of work — so the same model covers drainage, structures, lighting, signs and utilities as those asset classes are added.
What it affects
- Tree T-882affects
- Fence F-104part of
- Boundary renewal projectshares access with
- Drainage inspection
Where it's already being worked on
- Tree T-882inspected under
- Vegetation programmerecommendation
- Fell
Kinds of relationship
Five ways assets and work connect.
Spatial
Near, within, intersecting, on the same corridor.
A tree 1.7m from a fence line; a woodland inside the highway boundary.
Operational
Affects, requires, blocks, depends on.
Vegetation preventing access to a drainage outfall.
Project
Assets and work in different projects on the same ground.
A vegetation programme and a boundary renewal on one junction.
Work dependencies
Must be done before; can be delivered with.
Felling before fence replacement; fence removal before felling.
Coordination opportunities
Open work close together across projects.
Three planned interventions within 250m that could share traffic management.
Human validation
Arbrium suggests. People confirm.
Relationships come from spatial analysis, configurable rules, inspection findings and people. Every one records how it was created, the evidence behind it — such as the distance between the assets — and who confirmed or rejected it.
A suggestion never becomes an operational dependency on its own. Rejected suggestions stay on the record so they aren't raised again.
Respecting permissions
A relationship is only shown to someone who can see both ends of it. Where related work exists in a project you can't access, Arbrium says so — without revealing what it is.
Bounded, event-driven analysis
Rules run when work is created or an asset moves, using bounded spatial searches — not a sweep of the whole network — so analysis stays fast as asset counts grow.
In the product
Where you'll see it.
- Available
Relationships panel on every asset
Suggestions to review, confirmed dependencies, planned work nearby, related projects.
- Available
Rule-based suggestions
Boundary work near recommended vegetation work, with configurable distance.
- Available
Related infrastructure activity for a project
Dependencies, related projects, nearby planned interventions and coordination opportunities.
- Available
Show related on the map
Each marker explains why it's relevant — distance, recommendation, project.
- Available
Relationship graph
The same relationships as a diagram, filterable by type.
- Available
Trees, belts, woodland and boundary fencing
- Planned
Drainage, structures, lighting and signs
- Planned
More relationship rules, configurable per organisation
- Planned
AI relational assistant
Questions about what affects what, answered from the relationship record.