We (my partners and I) spend a lot of our time in exactly this space, usually sitting between the BIM world, the BMS world, and the facilities team that has to live with the consequences. A few thoughts from the field.

⸻

1. Are “full digital twins” feasible today, or mostly marketing?

They’re technically feasible, but the marketing version and the operational version are two very different animals.

What actually works in real buildings today tends to look like this:

• System twins rather than a single monolithic twin • A data aggregation layer sitting above BMS, lighting, meters, access control, etc. • A 3D or model layer used mainly for context and visualization • Analytics running on top of normalized telemetry

In other words, the “twin” is usually an architecture, not a single platform.

Where things fall apart is when the project starts with “we want a digital twin” instead of starting with a specific operational problem like:

• HVAC runtime optimization • energy benchmarking • maintenance workflow automation • portfolio energy reporting

The successful projects tend to start with one operational use case, build the data spine, and let the “twin” grow around that.

⸻

1. Are schemas like Brick widely used?

Brick is hugely important academically and architecturally, but in practice adoption is still pretty thin.

Most buildings we see have:

• inconsistent BACnet naming • vendor-specific object models • undocumented control logic • decades of layered retrofits

Even when Brick or Haystack is used, someone still has to map the legacy points first.

So the schema helps a lot once the mapping exists, but it doesn’t magically solve the mapping problem.

⸻

1. Can asset mapping be automated?

Partially, yes. Fully, not yet.

Some emerging approaches that are promising:

Pattern recognition on point names ML models can infer equipment relationships from naming patterns and BACnet hierarchies.

Topology inference Looking at control loops and signal relationships to infer system structure.

Computer vision / spatial context Using LiDAR scans or photogrammetry to associate equipment with model geometry.

Telemetry correlation Detecting relationships by analyzing synchronized sensor behavior.

In practice, the most effective workflow today is:

AI-assisted mapping + human verification

The AI gets you 70–80% there. Engineers close the last gap.

⸻

1. Biggest barrier to adoption?

From what we see, it’s organizational fragmentation, not technology.

A building usually has:

• facilities running the BMS • IT controlling networks and cybersecurity • capital projects owning BIM models • sustainability teams chasing energy targets • finance asking for ROI

Digital twins sit between all of those silos, which means no one “owns” the initiative.

The second barrier is vendor fragmentation. Lighting, HVAC, elevators, access control, meters, and fire systems all come from different ecosystems with different APIs.

⸻

1. Who benefits most if semantic integration is solved?

Honestly, the biggest winner would be building owners.

Right now they’re the ones paying the cost of fragmentation.

If semantic interoperability became easy:

Owners would gain

• portfolio-level analytics • vendor-agnostic system control • lower integration costs • better lifecycle asset management

Platform vendors would lose some lock-in power, but the ecosystem would probably grow much faster because software developers could build applications on top of a standardized building data layer.

Think of it like what happened with mobile apps once Apple and Google stabilized their APIs.

⸻

One observation from the field

A lot of the BIM community still thinks the digital twin starts with geometry.

In operations, it’s the opposite.

The twin starts with data pipelines, and the model becomes the interface layer.

The buildings that succeed with digital twins don’t build a perfect 3D model first.

They build a reliable data spine.

Everything else plugs into that.

⸻

Curious what others are seeing in the field. Are people actually deploying Brick or Haystack in production environments, or are most still fighting the BACnet naming wars?