Chapter 3 of the BIM Handbook discusses interoperability, a
key component in an efficient, more painless workflow1. The chapter
was dense in its’ technicality but discussed key practices for the cohesion of
software and systems in building modeling. Many aspects of interoperability
were brought up; my blog discusses a current BIM server application, XML files
as a common language, and how each relate to interoperability within models and
files.
One topic discussed was the many BIM servers used in current
practices. One of the mentioned servers was ProjectWise (Bentley ProjectWise
Integration Server), which I used throughout my last co-op. ProjectWise used
read-write transactions to manage and edit data at the file level. That is,
files across the database can only be accessed for edits one at a time. Also
incorporating ProjectWise Navigator for more seamless inclusion of the data’s
native file format into the database, ProjectWise is an extremely robust
program, having the ability to host thousands of files in countless formats. On
the other hand, ProjectWise works at the file level, which means that data can
only be managed in ProjectWise to this extent. Below this, at object or object
instances, data must be accessed explicitly in its’ file, and written back to
the server once edited. Alongside this, as files can only be accessed by one
user at a time, this limits interoperability between users; a Cloud-like server
hosting multiple users who can collaborate on files together at the same time would
be ideal.
Chapter 3 of the reading also discussed, among many other
file formats, XML files. XML files are used similarly to DXF files, which were
also discussed; these formats allow for the export and import of data between
various modeling programs. A program may not be able to access a CAD model's
native DWG or DGN format, but can read the data if it is introduced as a DXF.
This type of file usage is the key component of this entire chapter in my
opinion, as moving data between programs and software is often a nightmare. XML
files are used frequently in model development and production; for example,
when many projects are started, surveys are taken to develop site information.
This data can be exported as a LandXML, and imported into your preferred CAD
program as contours and elevation information for the model. XML files are not
limited to early-stage applications for projects either, as the handbook also
discusses DWF and 3D PDF files as XML format. These formats allow for 3D visual
mapping of the model.
Works Cited
1)
Eastman, Charles M. BIM Handbook : A Guide To
Building Information Modeling For Owners, Managers, Designers, Engineers And
Contractors. Hoboken, NJ: Wiley, 2011. eBook Collection (EBSCOhost). Web. 17
Jan. 2016.
Comments
http://ae-510-ay15-16.blogspot.com/2016/01/b2-dianna-vogel-interoperability.html#comment-form
To Dianna Vogel - Prior to reading both your post and the reading itself, I hadn't heard of IFC or Express. The inclusion of aspects like concrete reinforcement in properties in the model is huge, but there's a lot more that can be done here before the BIM end of the model is truly comprehensive. The handbooks read were from multiple years ago, so it would be interesting to see current stages and applications of these properties. My post was about the same chapter, but discussed a couple different topics about software and file applications, so I enjoyed reading this.
http://ae-510-ay15-16.blogspot.com/2016/01/b2-group-b-cummings.html#comment-form
To Bryan Cummings - The last paragraph was a nice expansion on current stages of software and model interoperability, and I completely agree with it. First, as you said, the technology is still in development, and the pieces that have been explored the most are simply those that have the most applications. It will take more time (and interest in BIM) to fill in the gaps, but I can't imagine more and more comprehensive uses of BIM are far behind. Secondly, the rift between the software designers and the engineers is apparent. It's much smaller than it once was, but new software often gets brought out before the engineering application can notice flaws or holes. Larger companies often have a software group tailor downloaded programs to their own needs, but this kind of development only creates ease of functionality for users; expansion of the base products is what helps push new applications of the software forward.
Comments
http://ae-510-ay15-16.blogspot.com/2016/01/b2-dianna-vogel-interoperability.html#comment-form
To Dianna Vogel - Prior to reading both your post and the reading itself, I hadn't heard of IFC or Express. The inclusion of aspects like concrete reinforcement in properties in the model is huge, but there's a lot more that can be done here before the BIM end of the model is truly comprehensive. The handbooks read were from multiple years ago, so it would be interesting to see current stages and applications of these properties. My post was about the same chapter, but discussed a couple different topics about software and file applications, so I enjoyed reading this.
http://ae-510-ay15-16.blogspot.com/2016/01/b2-group-b-cummings.html#comment-form
To Bryan Cummings - The last paragraph was a nice expansion on current stages of software and model interoperability, and I completely agree with it. First, as you said, the technology is still in development, and the pieces that have been explored the most are simply those that have the most applications. It will take more time (and interest in BIM) to fill in the gaps, but I can't imagine more and more comprehensive uses of BIM are far behind. Secondly, the rift between the software designers and the engineers is apparent. It's much smaller than it once was, but new software often gets brought out before the engineering application can notice flaws or holes. Larger companies often have a software group tailor downloaded programs to their own needs, but this kind of development only creates ease of functionality for users; expansion of the base products is what helps push new applications of the software forward.
Alex,
ReplyDeleteYou read a different chapter of the BIM Handbook than I did, but your discussion about interoperability relates to what I talked about regarding collaboration in the design process of a building project. Before reading your post, I was not familiar with ProjectWise or XML files, but I now understand how they make the system of exchanging modeling information more efficient. Chapter 5 of the handbook introduces two workflow methods which involve file exchanges between the designer and the structural engineer in order to modify drawings as the project progresses. Having the capability to make changes in different programs and have files that shows these changes is truly beneficial. It is very interesting to see how the data exchange process is advancing to enhance building design and to make it more easily accessible to multiple parties using various programs.
Alex,
ReplyDeleteYou focused on a different part of the chapter than I did; however, I enjoyed the information you pointed out. I have never personally used ProjectWise at either of my Co-op’s, but its ability to manage so many of files at one time seems extremely useful. Nevertheless, interoperability is an extremely important factor when it comes to file share systems. Hopefully ProjectWise can evolve into a system that can allow multiple users to make changes at the same time (possibly through a cloud-like server as you mentioned), because that is what is necessary in the construction field today. In the future, the same concept of multiple people working on a Google Drive document could be incorporated in to a BIM system. Obviously, BIM systems are much more complex, but that is what the technology is moving towards.
Hello Alex,
ReplyDeleteHaving firsthand experience with Bentley must give you a better perspective into how interoperability works. I myself have not worked with it but it seems like a useful application. Having worked exclusively with AutoCAD in my previous Co-op I can relate to the limitations certain engineering programs can have, especially in regards to file management. Having the limitation of only one person being able to edit a file at a time, while an understandable constraint, certainly limits the capabilities of interoperability and slows down the process as a whole. I think a plausible future for systems like this would be to allow for multiple users to interact with the same file, whether it be a database, or a drawing in order to promote collaboration.