From c88de7f86aaf30c057568b5ef2f336a8e65df7a7 Mon Sep 17 00:00:00 2001 From: rvba Date: Sun, 23 Nov 2025 10:26:54 +0100 Subject: [PATCH] Actualiser README.md --- README.md | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d5c315d..b9d3470 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,33 @@ ## The Challenge -streaming data : quicker, faster, stronger +* [Problem statement](https://github.com/vyzn-tech/ifc-data-bus?tab=readme-ov-file#problem-statement) + +## The Challenge + +## 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 + +> 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 ## ifc-data-bus 🚐