Asset Modelling 3.0
Making Complex Systems Legible
Modern asset systems are powerful. But nearly impossible to understand.
The Problem
Systems Built for Power,
Not for People
Enterprise asset platforms hold critical infrastructure data. Yet the people who rely on them can barely navigate them.
Fragmented across tools
No single source of truth. Context lives in spreadsheets, tickets, and memory.
Dependencies are hidden
Assets connect to other assets. Those connections are invisible by default.
Failures are hard to trace
When something breaks, pinpointing the cause requires hours of investigation.
Requires tribal knowledge
Critical context lives in the heads of two or three senior engineers.
The Reality
Users don't struggle with data. They struggle with relationships.
What they see
Rows. Columns. IDs. Status flags. A table that answers "what" but never "why."
What they need
Context. Cause and effect. A view that shows how one asset affects everything downstream.
The Insight
To fix systems,
users must see cause and effect.
Not just assets. Not just status. The relationships between them.
Current mental model
A list of things that exist.
Required mental model
A network of things that interact.
Design response
Make the network visible, explorable, and trustworthy.
The Shift
From Asset Management
to System Intelligence
The interface stopped being a database viewer. It became a system map.
Core Concept
Model as a System
Nodes
Every asset is a node. Named, typed, and stateful at a glance.
Edges
Dependencies are first-class. Relationships have direction, weight, and meaning.
System
The whole is a living network. It evolves as assets change.
Key Experience 1
Relationship Workspace
The canvas lets users explore their entire asset network at once. Not a list. A map.
Failure path tracing
Click any asset. See exactly which nodes are at risk downstream.
Upstream / downstream visibility
Understand impact before making a change. No surprises.
System health awareness
Color-coded states surface critical issues without a single query.
Key Experience 2
Guided Modelling
Building a model used to require deep system knowledge. We replaced that with structure.
A step-by-step creation flow removes ambiguity. Users build correctly the first time.
1
Structured creation
Each step is scoped. Users only see what is relevant to that decision.
2
Reduced errors
Inline validation catches mistakes before they propagate into the model.
3
Faster onboarding
New users model independently within their first session.
Key Experience 3
AI as Operator

User: "Why is Tower A failing?"
01
Highlights failing nodes
The graph instantly focuses on the affected asset and its neighbors.
02
Shows dependency chain
Every upstream cause is surfaced in sequence, with context.
03
Suggests fixes
Actionable recommendations, not a chat log. One click to resolve.
AI = action, not conversation. It operates on the model directly.
System Feedback
Trust is a Design Decision
Validation states
Every model element reports its status. Uncertainty is never silent.
Visible errors
Errors surface inline, in context. Users fix issues where they find them.
Model confidence
A completeness score tells users when a model is ready to be trusted.
Outcome
What Changed
60%
Faster model creation
Guided flow cut average build time significantly across user testing sessions.
3x
Fewer critical errors
Inline validation reduced model defects introduced during the creation phase.
80%
Decision confidence
Users reported being significantly more confident acting on model outputs.
40%
Reduced expert dependency
Teams resolved issues independently, without escalating to senior engineers.

The system did not just improve the tool. It redistributed knowledge across the team.
Clarity
over complexity.
Complex systems don't need more data. They need clarity.
Asset Modelling 3.0 is that clarity, by design.