ImmerTwin DataHub

Your records.
Connected to your reality.

Give assets, locations and activities a consistent data foundation that other modules can use throughout your digital twin.

Illustrative concept · Configuration agreed for your project

A clear role in your platform

Your records. Connected to your reality.

A configuration shaped around your audience, content and objectives.

The structured-data module that holds records, fields, relationships and status information used by other modules. Unlike Vault, which manages files and collections, DataHub provides a consistent data model for assets, people, locations, activities or cases. It can begin with manual or scheduled imports and scale to validated, relational or near-real-time data connected to operational and enterprise systems.

Give the digital twin a consistent set of structured records that other modules can use. DataHub manages records and relationships; Vault manages document and media collections, while Connect handles external-system exchanges.

ImmerTwin DataHub module tiers

What’s included in your DataHub?

Choose the level your project needs. Volumes, capabilities and responsibilities are confirmed in your agreed scope.

Base

The essentials

Data
1 dataset with up to 500 records and 10 fields.
Import
manual CSV upload.
Logic
standard field types; no relationships.
Best fit
A small asset list or location directory.

Plus

Expanded capabilities

Data
up to 3 datasets and 5,000 records total; 25 fields per dataset.
Import
scheduled file import.
Logic
validation and simple cross-references.
Best fit
Teams managing related directories or operational lists.

Premium

Advanced configuration

Data
up to 10 datasets and 50,000 records total; 50 fields per dataset.
Import
API sync up to hourly.
Logic
relational data, transformations, audit history and access rules.
Best fit
Larger operations requiring scheduled data synchronisation.

Bespoke

Tailored to your project

Configuration
Custom data models and scale; real-time or event-driven synchronisation; complex validation and business rules; master-data, warehouse or sector-system integration.
Best fit
Enterprise data models or specialist sector records.

Built around real applications

Where could DataHub take your project?

Suggested applications and starting tiers to discuss and adapt to your requirements.

Ops / Make

Maintain asset identifiers, locations and agreed status fields.

Make consistent asset information available in spatial context.

Build / Restore

Organise project or handover records with related locations.

Reduce repeated re-entry of the same project information.

Health / Education

Maintain approved facility, department or equipment directories.

Give teams a consistent source for directory content.

Enterprise / Travel

Connect portfolio records to scheduled external data feeds.

Support current information across multiple experiences.

Connected to your platform

Build on the modules around you.

These connections depend on the selected modules and agreed configuration.

01

DataHub + Vault

Links structured records to documents, images and manuals.

02

DataHub + Access

Controls which audiences can view or update datasets.

03

DataHub + Connect

Maps and synchronises records with external systems.

04

DataHub + Protect

Relates inspection findings, risks, actions and status to assets or locations.

05

DataHub + Learn

Links configured learning assignments and completion records to roles and locations. Learn provides the structured learning and assessment workflow.

06

DataHub + AR

Supplies labels, asset details and status values to spatial overlays.

07

DataHub + Forms

Creates or updates records from validated submissions.

08

DataHub + Timeline

Supplies dated records and milestones to configured timelines.

09

DataHub + BIM

Links asset records to model elements using agreed identifiers.

10

DataHub + Maps

Supplies location and status information for map pins or layers.

Terms, explained

Clear terms. Informed choices.

A record is one item, such as an asset. A field stores one attribute, such as its identifier. A relationship links records. API synchronisation exchanges data between systems.

Built around your project

Start with the questions that matter.

Which system owns each field? What volumes, relationships, update frequency and retention rules are needed?

01

Define the scope

Agree the content, quantities, audience and any connected-module requirements.

02

Agree ownership

Confirm content ownership, client approvals and who maintains the information.

03

Plan ongoing support

Ongoing support and response commitments follow your selected Service Layer.

ImmerTwin DataHub

Make DataHub part of your experience.

Let’s talk about your audience, your content and the configuration that fits.

Talk to ImmerTwin