Book a demo
Digital twin

A model of the building
that knows what it is doing.

A model earns its cost when the asset inside it is the same asset record the alarms, the analytics and the work orders are already using. Ours is bound to that registry rather than maintained alongside it, so it does not quietly go out of date the way a hand-updated model does.

Live

Select something. It answers.

Illustrative readings below, but the interaction is the product: the model is a way into the data, not a picture of it.

What is in it

Seven things that make a twin operational.

The model
A 3D model of the building, or a photographic walkthrough of the space as it actually is. Both carry the same live data — the choice is about what the site already has, not about capability.
Where it comes from
If the project left a BIM model behind, its geometry is where the twin starts once it is exported to a standard 3D format. We are not a BIM authoring or coordination tool — that work belongs to design and construction and is finished by the time this matters. What we add is the operational layer BIM was never meant to carry: live values, live status, live work.
The assets
Plant is attached to the model, so selecting a unit opens its live points, its status and its open work rather than a static label someone typed once.
The floors
Move floor by floor with alarm and equipment counts per level, so the twin answers "where is the problem" before anyone opens a graphic.
The overlays
Conditions rendered across the space as a gradient rather than a list of point values — because a room being warm is a shape, not a number.
The tags
Temperature, air and HVAC, electrical and water pinned in place, so a walkthrough carries the same instrumentation the plant room does.
The link back
Everything in the twin is the same asset record the rest of the platform uses — one registry, so nothing drifts out of step.
The honest version

What ours does, and what it does not.

This one does not detect a fault, verify a saving or close a job — the platform underneath does all of that. What the model adds is an estate that is legible to people who do not read control graphics, which is most of the people who have to make decisions about it.

It also mirrors the building as it is, not as it might be. Simulation is on our roadmap rather than in the product, and we would rather say so than let the word imply it.

So the twin here sits on top of the same platform as everything else: fault detection finds the problem, work management closes it, and measurement and verification proves what the fix returned. The model is where you see it happen.

  • 3D model or photographic walkthrough, both live
  • Equipment bound to the model, not labelled on it
  • Live points and status on selection
  • Floor-by-floor alarm and equipment counts
  • Condition overlays across the space
  • Tagged temperature, air, electrical and water
  • One asset registry shared with every other module

Worth it when it is wired to something

If the model is updated by hand it becomes wrong within a month. Attached to a live data layer and one asset registry, it stays true because it is reading the same records everything else is.

Book a demoSee the whole platform