The platform · The three questions

Three questions every twin must answer.

The twin works. Then it stalls. If you have watched enough industrial enterprises try, you know it is rarely a technology problem. It stalls because three questions were never answered at the foundation.

  1. Identity & lifecycleWhat is the thing we are modelling, and how does it change over time?
  2. Trust & governanceWho has the right to see it, change it, or act on it?
  3. Structured knowledgeWhat do we actually know about it, and where does that knowledge live?
Nexus

Identity that survives change.

The problem

A turbine today is not the same turbine it was five years ago, even with the same serial number. Components have been swapped, firmware upgraded, ownership transferred. Most platforms treat identity as a fixed label and lifecycle as an afterthought - so the twin drifts from physical reality within months of going live.


The platform

Hubbiot Nexus treats identity, structure, lifecycle and lineage as first-class concepts. Models carry versions. Individuals carry their real composition. Every event is recorded as a fact in one graph, so the twin is always the asset as it is today - and as it was on any day before.

Modelv3type · versioned
instance_of
IndividualSN-4471
RotorSensor packController v2
  1. Commissioned
  2. Upgraded
  3. Now
Access

Permission that follows the asset.

The problem

An asset crosses many organisations - manufacturer, dealer, operator, service partner, regulator. Each needs a different slice of the same record. Bolt-on permission models, built as lists of roles, turn brittle the moment that complexity is real.


The platform

Hubbiot Access weaves trust into the platform from the start. A rule is a path through the twin - member → training → asset type → asset - not a separate list of roles to maintain. Each party sees exactly its slice, deny wins, priorities are explicit and every decision is logged. Test a decision before it goes live, or draft the rule with Hubbiot AI.

Trust follows the asset
Service partneronly the machines they maintain
Regulatorthe lineage of a recalled batch
Operatortheir own fleet, end to end
Knowledge

The understanding, not just the data.

The problem

Most platforms focus on data but ignore knowledge. Documentation scatters across systems and shared drives; expertise walks out the door when people leave. An assistant pointed at that pile answers confidently from the wrong manual.


The platform

Hubbiot Knowledge models product structure and captures expertise in a form that is navigable and durable - linked to the right version of the right machine. Hubbiot AI, EU-sovereign by design, answers grounded in the correct document for this exact unit.

Linked to the right versionPump · v2
ProcedureSpec sheetExpert note
AI assistant

Grounded in the correct document for this exact machine.

Data model

A three-tier hierarchy, instantiated into reality.

Define a product once and version it as engineering evolves. Every unit ever built inherits a consistent, governed structure - and carries its own composition, history and owner on top.

Type graph · Article number
Producthas_subsystemSubSystemhas_componentComponent

Asset Type Blueprint · Article no.

Define a product once and version it as engineering evolves - every unit ever built inherits a consistent, governed structure, so the whole product line stays coherent.

Instance graph · Serial number
Individual SN-4471
Actual compositionRotor · Sensor pack · Controller v2
Event historyCommissioned → Upgraded → Serviced

Asset Individual Real unit · Serial no.

Every machine carries its own true composition, history and owner - so you answer precisely for this exact unit in the field, not just the generic model.

TimeMachine

Any view, any point in history.

Reconstruct any individual - or the whole fleet - as it was at any moment, by reading recorded events and the periods they were in effect. The history is in the data, never replayed.

Which firmware was installed when the fault first appeared?
What was inside this machine on the day of the warranty claim?
Who owned it during the incident?
  1. Commissioned
  2. Firmware v4
  3. Warranty claim
  4. Ownership change
  5. Now
Fleet-scale patterns

When the same behaviour emerges across many machines, the platform draws the pattern at a global level - then rewinds to pinpoint the events that led up to it.

Premium tier

Base time travel ships in Hubbiot Nexus. TimeMachine is the premium tier - forensic queries, audit and retention windows.

Why it holds

Four rings around the asset. Each one harder to cross.

Apps and dashboards are cheap to generate with AI. A trusted, multi-party record of every asset is not. At the core sits the governed record; around it, four properties that compound with time.

History compounds

Every year adds configuration, events and knowledge per asset. Switching means leaving that history behind.

A neutral seat between companies

OEMs, operators, service partners and regulators share data with a neutral custodian - not with a rival's platform.

Sovereign by architecture

On our own European infrastructure or the customer's own servers, from day one. Hard for stack-bound incumbents to retrofit.

See how the three pillars show up in the product.

Explore the productsJoin the waiting list