Which building information is best conveyed in 3D, and which still requires 2D?
The 2D view gives the best annotations of dimensions for the specifics of the building. In 3D view its really hard. Th 2D view also lays out what is in the building better like a typical floor plan is much easier to read than a 3d model of where things in a building go, since there are things like scope boxes or selection boxes that need to be used inorder to see these details in a 3D view.
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?
Schedules can support the estimates since the schedules give a good numerical sense of what is going on. For example, maybe somewhere in the model a room or a wall was accidentally deleted. this would be very apparent in the schedule since the area for a particular room would seem out of place.
◦ What is the danger of a schedule that is accurate about the model but wrong about the building?
A lot of the data is inputted to an estimate. Since these are estimate for the model they may not apply to the actual building. things like occupancy.
◦ What did your calculated field reveal that the plans did not?
My calculated fields revealed the residential unit distribution across both buildings which none of my plans reveal unless I open two plans and count everything
You published two versions and compared them.
◦ Why does version history matter more on a shared model than a personal one?
version history matters more on a shared model because when someone changes something in one version, its important to have a back up to fall back to and to see what edits have been made, because you are not the only person working on the model, so you also can’t keep track of everything that has been done to the model
◦ If a consultant says their work was based on last week's version, what do you need to be able to tell them?
I need to be able to tell them what has been changed in the new version.
◦ When should a model be formally issued rather than just saved?
When major changes happened and people outside of just the immediate team needs to see.