Which building information is best conveyed in 3D, and which still requires 2D?
I think the interior of the building is best conveyed in 2D to communicate the apartment layout, spacing, furniture orientation so this would be very useful to interior designers and architects. However, the 3D view would be good for viewers to see how the building would look like which is perfect for clients (to help decide what they want) and is good for skilled professionals to view their work in a realistic way.
The 3D view fails to communicate the door swing of doors within the building. This is crucial to know for checking if furniture fits into building with door.
The same location needs to be shown differently to different audiences.
Each stakeholder needs to be shown the same spot but with varying amounts of detail. A client needs to see the view of the building to understand how the building would look on the exterior and interior to see if it meets their specification. A contractor might need to see the construction drawings, the schedules of the different materials and parts needed to build that spot. A code official may need to see the schedules to see if the building is able to serve its specified number of people. They could compare the numbers in the schedule to the code limits.
The risk of showing everyone the same view is making some stakeholders confused with over information or not giving some stakeholders enough information to complete their tasks.
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.
Version history matters more for shared work as mistakes and conflicting edits are more likely to happen with different people working on the model so it is important to have old versions of the project for the team to go back to. This reduces lost work. It also helps co-workers understand each others work better, knowing which version each person made their design or analysis on.
If a consultant used last week’s version, you need to identify the exact version they used and what has changed since then. This will enable you to highlight next steps. A model should be formally issued to the cloud on an agreed day that everyone on the team is aware of so that everyone is always working on the correct version and there are no conflicting versions.