Why asset lifecycle data has no natural owner

If you have watched enough industrial enterprises try to build digital twin platforms, a pattern emerges that has nothing to do with technology.

A programme is launched and someone is appointed to lead it. Within a year, the leader is being pulled in several directions.

Engineering wants the platform to serve design, software distribution and configuration data. Service wants it to carry service lifecycle, service sales and field history. Aftermarket wants pricing and installed base intelligence. Sales wants visibility into upgrades and renewals. Each division or business area has a legitimate claim. None of them owns the whole. And the programme leader, whoever they are, answers to a division that only sees part of the picture. Sometimes there is a CTO function or even a role, but it rarely hosts the mission or authority required to sustain digital asset data across the organisation.

The horizontal truth about vertical organisations

Physical products have lifecycles that are inherently horizontal. An asset is designed by engineering, manufactured by operations, marketed by marketing, sold by sales, serviced by aftermarket, and eventually decommissioned or resold by yet another actor. At each step, data about the asset accumulates: specifications, configurations, events, histories, obligations. Together, this data tells the full story of the asset.

Industrial enterprises, however, are not organised horizontally. They are organised vertically: by function, by division, by P&L or by region. Each vertical has its own systems, its own budget, its own priorities, and its own measure of success. The data about an asset lives in pieces, scattered across these verticals, each piece shaped by the needs of the division that happens to hold it.

The asset, which is horizontal by nature, has no natural home in an organisation that is vertical by design.

What this looks like in practice

The consequences are everywhere, once you know where to look.

Aftermarket pricing depends on bill of materials data that engineering owns but does not update for commercial use. Field service decisions require configuration history that service collects but struggles to share upstream. Field engineers need documentation that technical publications produce but in a format that does not fit the tools they actually use. Digital twin programmes get funded from innovation or IT budgets, but neither innovation nor IT runs the lifecycle they are trying to model. Acquired product lines arrive with fractured installed base data that nobody has the authority, or the budget, to reconcile, and it wasn't recognised as an activity during the due diligence of the acquired company.

Each of these is a symptom of the same root cause: the artefact's lifecycle crosses every divisional boundary, but the organisation has no structural place for something that crosses every divisional boundary.

Why reorganising will not fix it

The instinct, when the problem becomes visible, is to reorganise. Create a digital product team, appoint a head of platform or consolidate data ownership into a central function.

These moves sometimes help, but they rarely solve the underlying issue. The new central function is still funded by a vertical budget. It still reports into a vertical hierarchy. It still has to negotiate with the divisions whose data it is trying to coordinate. The horizontal work remains inconvenient for the vertical organisation, and over time, the verticals reassert themselves. The central function either becomes quietly marginalised or is absorbed back into one of the divisions that gave rise to the problem in the first place.

Reorganisation assumes the structure is wrong. In most cases, the structure is correct for running the business day to day. It is only wrong for managing the lifecycle of the thing the business produces.

A platform that does not belong to any vertical

The alternative is to stop trying to force the lifecycle into a vertical container, and instead give it a platform layer that deliberately sits across the verticals without belonging to any of them.

This is a different kind of architectural decision than most enterprises are used to making. It is not about choosing a cloud provider or a vendor. It is about accepting that the artefact's lifecycle is horizontal, building a foundation that respects that fact, and letting each vertical connect to the foundation on its own terms.

This conviction shapes every part of how we have designed the Hubbiot platform.

Nexus models identity and lifecycle as first class concepts, so the asset has a single, authoritative home regardless of which division is acting on it at any given moment. Access governs who can see and act on what, across organisations and verticals, so legitimate work is enabled without compromising trust. Knowledge gives structure to the documentation and expertise that accumulates around the asset over time, so it remains navigable as people, systems, and divisions change.

None of these belong to a single vertical and that is the point.

Built to sit across, built to endure

The verticals of an industrial enterprise are relatively stable, but they are not permanent. Divisions are reorganised, functions are outsourced and products are acquired or divested. A platform tied to today's divisional structure will not survive the first meaningful reorganisation.

The horizontal layer has to outlast the vertical arrangements that surround it. It has to be portable and it has to be designed with the assumption that everything around it will change, because over the lifetime of an industrial asset, it will.

In the new reality the World has seen in recent years, it also has to be sovereign.

These features are all structural starting points for what we are building.

What comes next

The first release of the Hubbiot platform is designed to give enterprises the horizontal foundation their asset lifecycles have always needed, without requiring the organisational change that has never quite worked.

If this resonates, we would welcome the conversation.