What digital twins in asset lifecycle management actually needs to get right

After years of working with industrial and enterprise systems, we keep seeing the same pattern. An organisation invests in an product asset digital twin programme. The technology works. Dashboards appear. Data flows. And yet, within a year or two, the initiative quietly stalls. Teams lose confidence. Executives lose patience. The programme either gets quietly shelved or scaled back to a fraction of its original ambition.

The root cause is almost never a missing algorithm or an inadequate cloud platform. It is something more fundamental.

The three questions nobody wants to answer first

Digital twins become fragile when three foundational questions remain unresolved. These questions are deceptively simple, but getting them wrong poisons everything built on top.

What exactly is the thing we are modelling, and how does it change over time?

This is the identity and lifecycle question. In industrial and long lifecycle systems, a "thing" is not static. Products get upgraded, serviced, split apart, reassembled, resold, and eventually decommissioned. A turbine in a power plant today is not the same turbine it was five years ago, even if it carries the same serial number. Components have been replaced. Firmware has been updated. Ownership may have shifted.

Most digital twin approaches treat identity as a fixed label and lifecycle as an afterthought. The result is a digital representation that diverges from physical reality over time, silently, until someone notices the data no longer makes sense.

This is the problem that sits at the heart of what we are building with Hubbiot Nexus. Nexus treats identity, business data structure, lifecycle, and lineage as first class concepts. Every artefact in the system can evolve, branch, and be traced across its full history. Not as a log bolted on afterwards, but as the fundamental data model itself.

Who has the right to see it, change it, or act on it?

This is the trust and governance question. In simple setups, access control is straightforward. But industrial systems are rarely simple. Products pass through multiple organisations during their lifetime: manufacturers, operators, service partners, regulators. Each has legitimate but different needs for access. Each expects a different level of visibility.

When governance is treated as a configuration task rather than a structural one, the result is brittle permission models that either block legitimate work or quietly allow access that should not exist. Neither outcome inspires confidence.

Hubbiot Access approaches this differently. Rather than layering access control on top of an existing data model, it is woven into the platform from the start. Identities, permissions, and audit trails are modelled with the same care as the artefacts themselves, across users, systems, and devices. For regulated and multi actor environments, this is not a nice to have. It is the difference between a platform you can trust and one you merely tolerate.

What do we actually know about it, and where does that knowledge live?

This is the structured understanding question. Industrial products accumulate vast amounts of knowledge over their lifetime: technical documentation, service records, procedures, specifications, and a great deal of experiential knowledge that exists only in the heads of experienced engineers.

Most digital twin platforms focus on data but ignore knowledge. The documentation sits in separate systems. The product hierarchies live in spreadsheets. The tribal knowledge walks out the door when people leave. The digital twin becomes an orphan, technically connected to sensors and dashboards but disconnected from the understanding needed to interpret what the data actually means.

Hubbiot Knowledge addresses this gap. It models product structures, links documentation and specifications to those structures, and captures expertise in a form that is navigable and durable. When connected to Nexus, knowledge becomes part of the twin itself, not a separate silo that someone has to remember to consult.

Why all three need to exist together

These three dimensions are not independent features. They are deeply interrelated.

Without clear identity and lifecycle, you cannot meaningfully control access, because you do not know what you are granting access to. Without proper governance, knowledge becomes either inaccessible or untrustworthy. Without structured knowledge, even a well modelled twin with perfect access control remains opaque to the people who need to work with it.

This is why approaches that treat digital twins as primarily a data integration problem tend to disappoint. They solve one dimension, perhaps well, but leave the other two unaddressed. And it is in the gaps between these dimensions that confidence erodes and adoption stalls.

Built for systems that outlast their first platform

There is one more pattern worth naming. Many of the systems we are focused on, industrial equipment, infrastructure, complex machines, have operational lifetimes measured in decades. The platforms and technologies used to manage them do not.

This creates a structural tension. The digital twin must outlive the technology it was built on. It must be portable. It must be sovereign. It must not become a dependency on a single vendor or cloud environment.

This conviction shapes everything about how we have designed the Hubbiot Platform. Sovereignty and portability are not features we plan to add later. They are architectural decisions made from day one.

What comes next

We are preparing the first release of the Hubbiot Platform, with Nexus, Access, and Knowledge as the initial product set. We are not building this in isolation. We believe the best way to get these foundations right is to work closely with a small number of enterprises who share the same convictions about lifecycle integrity, data sovereignty, and long term thinking.

If this resonates, we would welcome the conversation.