&nbsp;
&nbsp;


# ifc-data-horse 🐴

> **"There are no wheels yet, but the thing is running"**

## Meet the Team

* **Milovann Yanatchkov** : bug-hunter, aec-free-rider, associate-professor, kebab-case-lover.
* **Artem Igumnov** : civil-engineer, python-....

## The Challenge

* [Problem statement](https://github.com/vyzn-tech/ifc-data-bus?tab=readme-ov-file#problem-statement)

## Problem Statement

* Architects and planners rely on a **broad ecosystem of software tools**,
* yet **poor data integration between these tools creates major bottlenecks** in the design process.
* This fragmentation prevents holistic project optimization and slows down coordination.

### Data Stream 

* Although **OpenBIM** ✅ aims to support **interoperability**, it still lacks robust mechanisms for

> **bi-directional data exchange** ✅

* —particularly when it comes to **re-integrating data into CAD and CDE environments**.
*  **Existing initiatives often do not prioritize full OpenBIM compliance**, leaving a clear opportunity for alternative, standards-aligned solutions.

### 'Flat Modules' vs 'Monolithic Blob'

> At the same time, the emerging **modularized and layerized IFC5** standard ✅

* introduces new capabilities for more flexible, **fine-grained**, and machine-friendly data handling.
* These advances open the door to **new workflows** built around decentralized, **event-driven data exchange** rather than **monolithic file transfers**.

## The Story

### Zurich 2024

* [AEC hackathon](https://gitaec.org/rvba/docs/wiki/Zurich-hackathon) Zurich 2024

### Zurich 2025

![](images/gitaec_zurich_2025.png)

## ifc-data-bus 🚐



## [vyzn](https://www.vyzn.tech/en) : data-streaming-bim-platform

![](images/vyzn.jpeg)
