One of the most common challenges in BIM (Building Information Modeling) solutions today is the issue of BIM data exchange. You might wonder, what exactly is data exchange? Simply put, it refers to importing data from software A into software B. Although this sounds straightforward, it has consistently posed significant difficulties for both BIM software developers and users.
Why is it such a challenge? The reasons include:
1. “Language Barrier”
Different software platforms use vastly different data models, much like how two people speaking different languages—say, Chinese and English—face challenges in communication due to differences in vocabulary and grammar. Many have experienced the quirks of automatic translation tools. For example, the phrase “Study hard and make progress every day” might be translated as “Good Good Study, Day Day Up”, a rendition that only native Chinese speakers might understand. Unfortunately, most automatic translations are only truly comprehensible to the translation software itself.
Creating interfaces between BIM software is similar to building these translation tools, and achieving precise transformation of data models is extremely difficult. This leads to miscommunication or “false communication.” For instance, some software claim they can export DWG files, but those files can only be opened correctly by the originating software itself.
2. “I Don’t Have What You’re Looking For”
Consider a project using 3ds Max for complex architectural design. If you wanted to use Green Building Studio for building performance analysis, could you convert 3ds Max models into gbXML (the input file format for Green Building Studio)? Let’s explore this.
Generating a gbXML file requires detailed information about walls, floors, doors, windows, and more. However, a 3ds Max model typically contains only geometric data. Direct conversion is therefore not feasible.
An alternative might be to ask users to add extra information to the geometric entities in 3ds Max—such as identifying where walls and doors are located. But even this approach has limitations. gbXML also requires understanding the topological relationships between building components (e.g., how walls connect to other walls or floors), which is challenging to derive from geometric data alone. Would users need to define these topologies manually as well?
3. “What I Gave You Was Not What You Wanted”
Returning to the gbXML example, imagine a wall with a complex surface that spans multiple floors. When generating the gbXML file, this wall needs to be divided into sections corresponding to each floor. Developing interfaces to handle such cases requires complex geometric calculations.
Those experienced in computational geometry will recognize that this is far from a trivial task.
4. “You Can’t Digest What I Gave You”
In one project, I tried importing geometric models from Autodesk Inventor into Revit. However, I discovered that Inventor supports far more complex geometric shapes than Revit can handle. This kind of transformation isn’t feasible unless the complex Inventor models are simplified and broken down.
In summary, fully resolving these issues cannot rely solely on the interface programs. The BIM software itself must continually improve its internal capabilities to better support data exchange.
Must log in before commenting!
Sign Up