iViRTHRequest a Pilot

Helix: Identity and Digital Twins

The canonical identity and digital-twin layer across the iViRTH ecosystem. It gives people, assets, places and experiences a consistent way to be represented.

Request a PilotSee MTRX
Illustrative blue digital hand against a cyan background
Illustration

Four twins, one model

Human, Asset, Place and Experience.

Human Twin

A digital representation related to a person. Scope and data use are defined precisely per use case.

Asset Twin

A digital representation of a physical or logical asset, such as a bench, a charger or a piece of equipment.

Place Twin

A digital representation of a location, site or environment, such as a campus or a public space.

Experience Twin

A digital representation of an experience or journey, where the architecture supports it.

A digital twin is more than a 3D model

A 3D model shows what something looks like. A digital twin understands more.

What it isIdentity and classification.
Where it isLocation and spatial context.
What state it is inCondition and telemetry, where connected.
What happenedHistory and lifecycle.
What it is connected toRelationships.
What may happen nextPrediction, where implemented.
What should happen nowDecision support, where implemented.

The first five describe the twin model. The last two depend on analytics and AI that are implemented per project; they are not claimed for every deployment.

Identity: six questions Helix answers

Every connected world needs identity and a measure of trust.

Human identityWho are you?
Asset identityWhat is this?
Place identityWhere is this?
CredentialWhat have you earned?
PermissionWhat are you allowed to do?
TrustHow strongly has the identity been verified?

Helix can power, where implemented: single sign-on, digital credentials, institutional identity, access control, achievement and experience records, digital-twin provisioning and credential verification.

A digital twin does not inherently require biometrics. Helix is designed to support several identity and assurance mechanisms, with high-assurance authentication used only where appropriate and legally permitted.

What belongs in Helix

  • Human, Asset, Place and Experience Twins
  • Identity creation and lifecycle, subject to supported identity types
  • Twin records, identifiers, relationships and lifecycle state
  • Credentials, permissions and access policies where implemented
  • Twin APIs and integrations, documented by actual availability
  • Governance: data ownership, consent, retention, deletion, access control and auditability
3D illustration of a teal owl-shaped totem character
Concept illustration, not a deployed product

The twin graph

Twins become more useful when they understand relationships. Each link below is an example of how a twin graph can be modelled.

  1. Student
  2. Campus
  3. Buildings
  4. Laboratories
  5. Equipment
  6. Telemetry
  1. Student
  2. Event
  3. Place
  4. Assets
  1. Experience
  2. Credential
  3. Human Twin identity

A student is connected to a campus; the campus contains buildings, laboratories and equipment; equipment generates telemetry; an experience creates a credential that becomes part of the person's identity. Relationships, events, history and dependencies are what turn separate records into a graph. The graph carries references and context; where the underlying readings are stored is defined in each technical design.

Twin lifecycle

Nine steps from a physical thing to a twin that learns. Steps 7 to 9 depend on per-project analytics.

  1. Identify

    Give the entity a persistent identity.

  2. Connect

    Connect it to authorised physical and digital systems.

  3. Observe

    Capture signals through sensors, IoT, APIs, geospatial systems and human interaction.

  4. Twin

    Create its persistent digital representation.

  5. Synchronise

    Keep the representation aligned with the physical state.

  6. Understand

    Combine live data, history and relationships.

  7. Predict

    Identify patterns, anomalies and possible future states, where implemented.

  8. Act

    Recommend, automate or enable an action, with human oversight where needed.

  9. Learn

    Feed outcomes back into the system.

What Helix does not own

Helix is not the growth analytics dashboard and does not replace ViSE. It is not a separate product for every sector: applications may have different interfaces, but identity and twin definitions stay here.

Helix questions

Is Helix a database of sensor readings?

No. It owns identity and twin definitions. Where readings are stored is defined in each technical design.

Can a Human Twin be used without consent?

Scope and data use are defined per use case, with consent, retention and deletion stated.

Is Helix live today?

Capabilities are described by what is actually implemented in each deployment.

Does a digital twin need biometrics?

No. A digital twin does not inherently require biometric identification. Helix is designed to support multiple identity and assurance mechanisms.

What is the difference between a digital twin and a 3D model?

A 3D model shows appearance. A twin adds identity, location, state, history, relationships and, where implemented, prediction and decision support.

Where do the AI and analytics for twins come from?

Measurement is owned by ViSE. Models and inference are research under DoubleSlit and YNTR and are connected only where implemented and validated.

Ready to scope a pilot?

Tell us about your site and what you want to achieve. We respond with a site assessment plan and a quotation based on your configuration.

Request a PilotEmail us
Request a Pilot