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.
2D drawings/views are extremely helpful for legibility, organizing information that can be utilized by multiple involved parties, and attributing a hierarchy of information when necessary through separate 2D sheets that simplify some information while emphasizing what is key given a particular step in the process. In my building 3D views fail to clearly communicate which doors and windows belong to which units. In a 2D view tags/marks instantly make this clear.
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?
The risk of showing everyone the same view is causing confusion due to an over-abundance of information that might not even be relevant to a particular person’s job. Most importantly it might be information that they could be subject to misunderstanding. In order to filter information for the client, contractor, code official, or fabricator it might be helpful to create separate views of the same scenario in which different elements of the plan, section, elevation, building, etc. are hidden from view. Some plans might include extra tags or keys that are helpful to the specific individual viewing the document.
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?
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 matters most on a shared model because several people will be simultaneously working on a project at once. This requires tracking changes, progress, and versions in order to know how to back track when necessary and in order to understand what exactly developed over the span of say a few days… and also why. It is also important to have evidence of past versions and most up to date versions in order to communicate with others where the project should be picked up for further development. This likeley enables better communication and ownership over mistakes when it comes to developing an older version instead of a newer one. A model should probably be formally issued once it goes into the hands of any other collaborator, i.e. once the collaborative aspect of the project begins.