Which building information is best conveyed in 3D, and which still requires 2D?
◦ Which stakeholders need 2D drawings, and why has that not gone away?
◦ Give an example of something in your building a 3D view fails to communicate.
3D models are best used to show the building as a whole. This makes it easier to see how things will look in real life once the building is constructed. In 3D, the designer is able to see how things align and they are able to make sure things are place correctly in all three dimensions. While I was working on this module, I placed something in 2D that needed to be moved up/it had a height aspect to it, but I could not move it up until I switched from the 2D drawing to the 3D model. 2D models are very good at showing dimensions and they are helpful for naming rooms; these would not show up very well on a 3D model. Everyone involved with the architecture, engineering, and construction will need to work with the 2D drawings as these are the easiest to read and follow. The 3D building model as a whole does not do a great job of showing the wall assemblies. In the 3D model the view of the wall assemblies are limited because you can only see the exterior layers most of the time, but in a 2D model, you can see the overhead view of the wall assemblies to see each of the layers and understand the thickness.
The same location needs to be shown differently to different audiences.
◦ How would information at one spot be filtered for a client, a contractor, a code official and a fabricator?
◦ What is the risk of showing everyone the same view?
View templates enforce consistency across a set.
◦ What goes wrong on a real project when views are configured individually?
◦ Who should own the templates and standards, and why?
Your schedules pull information straight out of the model.
◦ How can schedules support procurement and model based estimating?
◦ What is the danger of a schedule that is accurate about the model but wrong about the building?
◦ What did your calculated field reveal that the plans did not?
The schedules are used to help organize all of the information in a condensed way. The information provided on these schedules can help understand the materials needed for a project, how much of each material, and the cost associated with each of the materials. If a schedule is accurate, but the model is inaccurate, there can be complications during the construction phase of the project. For example, if the schedule says you need 500 cf of concrete for something but the model is incorrect, the mistake will not be caught until there is an incorrect amount of material brought on site for the construction. This can then cause cost overruns and delays, two things that we actively try to avoid on construction projects. My calculated field was to figure out the area per occupant of each unit. This gave me an idea of how many people would be in the space as well as how many square feet of space there is per person living in a unit.
You published two versions and compared them.
◦ Why does version history matter more on a shared model than a personal one?
◦ If a consultant says their work was based on last week's version, what do you need to be able to tell them?
◦ When should a model be formally issued rather than just saved?
Version history on a shared model is important because people are relying on the same information. This means that there is more at stake is something is incorrect or if something changes without everyone being informed. Having a history of each version allows consultants to go back and look at what has changed in each version of the model, so if they find an inconsistency, they can see where it came from. If they say their work is based on a model from the previous week, I would need to figure out which version they were working off of and see what else has changed in the model since then. A model should be formally issued when there is specific information that needs to be shared and that everyone should be made aware of. Saving the model shows what has been done and if everything is going to plan or as expected, there is no need to formally issue a model every time something gets done.