Conceptual visualization of openBIMdisk showing object-level BIM diffs and blockchain-backed virtual storage.
International research team, September 12, 2025
A research team has introduced tSDT and openBIMdisk to make BIM exchanges leaner and traceable. tSDT records semantic, object-level differences so only real model edits become transactions, while openBIMdisk exposes a Blockchain 3.0 virtual disk that stores lightweight change records on-chain and keeps bulky files off-chain. In a modular construction pilot the method used about 0.007% of disk space for change records and returned version/object queries in around 5.3 ms. The approach reduces bandwidth and storage waste and offers fine-grained traceability, though larger trials and improved change-fusion remain next steps.
Engineers and builders could soon share building models faster and with far less storage waste after a 2025 engineering management study introduced a new exchange method and a supporting system. The paper reports that the traceable semantic differential transaction approach, shortened to tSDT, and its implementation, openBIMdisk, cut redundancy when recording BIM changes to an average of 0.007% of disk space and supported object‑level traceability with a reported response time of 5.3 ms. The work was validated in a pilot on a modular construction project and appears in a 2025 issue of an engineering management journal.
The research targets a familiar problem: teams working with building information models (BIM) usually exchange whole files even when only a few objects change. That practice wastes bandwidth and storage and makes it hard to track who changed what. The study presents tSDT, a method that records semantic differences at the object level rather than full files, and openBIMdisk, a Blockchain 3.0 virtual disk that stores those difference records, links them to blockchain services, and manages versions. In tests on a modular project, the method restored full BIM states while using virtually no extra space and kept response times low enough for practical version management.
Although modern standards for BIM data exchange exist, teams still face three linked problems: repeated transmission of unchanged objects, limited traceability of changes at the semantic or object level, and concerns about security or tampering when files are passed through centralized platforms. Blockchain is attractive for traceability and tamper resistance but cannot hold large BIM files directly. The new approach combines lightweight semantic change records with a blockchain‑connected virtual disk that links to other storage systems to balance size, traceability, and security.
The heart of the system is a method that computes semantic differences between BIM states. Instead of saving whole files, tSDT captures and records only the object‑level changes. The virtual disk manages these change records, keeps version links, and connects with blockchain services to give an auditable trail. The research team ran a pilot on a modular construction case to check storage, speed, and traceability. They report that rebuilding full models from the change records needed on average only 0.007% of disk space, and that the virtual disk handled version queries and object‑level trace lookups in about 5.3 ms.
Earlier work combined blockchain ledgers for metadata with off‑chain distributed file systems to avoid storing large files on chain. That hybrid approach used content hashes and smart contracts to verify integrity while keeping actual files in distributed storage. The new study extends that line by focusing on semantic diffs at the object level and by presenting a virtual disk concept that is designed to plug into multiple blockchain services. This lets practitioners get better traceability without paying the storage and throughput penalty of on‑chain file copies.
The authors note some caveats. Blockchain systems cannot realistically hold large binary BIM files, so hybrid storage remains necessary. The semantic diff method must scale to very large models and many concurrent users; further work is needed to improve performance for massive datasets and to tighten how fusion of changes ties into blockchain consensus. Practical adoption will also depend on integration with common BIM tools and on agreeing standards for semantic diff formats.
The tSDT method and the openBIMdisk prototype show a clear way to make BIM exchange leaner and more traceable. For teams that struggle with bloated file exchange, unclear change histories, or the risk of tampering, this model points to a workflow that keeps storage and network use low while improving the audit trail. Adoption will require software integration, field testing at larger scale, and work to make the method fit with BIM standards already in use.
tSDT stands for traceable semantic differential transaction. It records object‑level differences between BIM states so teams can save and share only what changed instead of whole files.
openBIMdisk is a prototype implementation that stores and manages tSDT records on a virtual disk linked to blockchain services. It handles version management and provides an auditable trail of changes.
In the pilot reported, restoring BIM changes used on average about 0.007% of disk space compared with storing full file copies for every change cycle.
The approach leverages blockchain properties—decentralized ledgers and linked hashes—for tamper resistance. Large files still live off‑chain, so integrity checks and secure linking are part of the design.
The method is designed to be integrated with BIM workflows, but widespread use requires connectors or plugins for common modeling tools and agreement on semantic diff formats.
The detailed study appears in a 2025 engineering management journal and is available via open access in the journal’s records.
| Feature | What it does | Reported metric / note |
|---|---|---|
| tSDT | Records semantic/object‑level changes instead of whole files | Reduces data redundancy dramatically |
| openBIMdisk | Virtual disk that manages change records and links them to blockchains | Designed for multiple blockchain services |
| Storage efficiency | Disk space used to store and restore all BIM changes | About 0.007% on average in pilot |
| Performance | Response time for version management and object trace lookups | Approximately 5.3 ms reported |
| Pilot use | Tested on a modular construction project | Validated storage and traceability claims |
| Limitations | Requires hybrid off‑chain storage and tool integration | Scaling and consensus integration need more work |
Minami‑Alps City, Yamanashi Prefecture, September 12, 2025 News Summary Tri Chemical Laboratories has closed ¥10 billion…
Peabody, Massachusetts, September 12, 2025 News Summary A Peabody developer secured a $13.9 million construction loan…
Oradell, New Jersey, September 12, 2025 News Summary Ascendia Bank, formerly Glen Rock Savings Bank, completed…
Portland, Oregon, September 12, 2025 News Summary The Portland Public Schools board voted 6-1 to expand…
Dublin, September 12, 2025 News Summary A Dublin-based market report finds the global AI-in-construction market currently…
Carlsbad, California, September 12, 2025 News Summary A private equity firm has completed a majority growth…