In practical computer operations, designers from various disciplines use specialized software to create, read, and modify information. To fully harness the benefits of BIM, seamless communication of data generated by dozens—or even tens—of different software programs is crucial. Furthermore, this data exchange should be highly automated, eliminating the need for manual interpretation, translation, or repetitive input. Computers must be able to automatically read, transmit, and store this information. To achieve such an automated information exchange, the author proposes three implementation methods:
a. Develop a single, comprehensive software solution supporting all disciplines and project phases. In this scenario, all professionals would use one software to complete different stages of a project. However, experts in construction and computing agree that this approach is nearly impossible to realize. Such software would require enormous hard drive capacity. Additionally, many construction professionals have limited manual workload, making it impractical to install such a bulky program. Current personal computer hardware is also insufficient to run such an all-encompassing application.
b. Enable direct information exchange between different software programs. This method allows data sharing either between software or between users. It is effective when only a few software applications are involved. However, as the number of software platforms grows—say, to 10 or more—the development cost rises exponentially. Moreover, software upgrades that alter data models require corresponding changes in all interfacing applications, increasing maintenance complexity.
c. Create an intermediate file format or data standard to unify all relevant software. Information exchange occurs through these intermediate files, introducing a “transfer” process. Developing a project-compatible standard that supports various workflow stages and professional technical requirements demands considerable time, effort, and research from experts across disciplines. Yet, once established, this standard provides long-term, high-value returns. The more software products that adopt this standard, the more valuable it becomes.
Comparing these methods, from a research and development cost perspective: the first approach’s cost is prohibitively high and impractical. Referencing data from the buildingsMART Alliance in the United States, the expense of developing and maintaining direct information exchange among 20 software programs is 20 times greater than that of creating and supporting a single intermediate data standard adopted by all 20 programs. In terms of adaptability, the third approach is best suited for diverse software ecosystems like BIM.
This is why today’s industry favors developing an open, structured data standard that supports automatic information exchange throughout all project lifecycle stages, across all project participants, and among all software products. The openness ensures broad compatibility, while the structured nature enables automation—both essential for fulfilling BIM’s mission.
Must log in before commenting!
Sign Up