Which building information is best conveyed in 3D, and which still requires 2D?
I think 3D views are better for understanding what a building actually looks like and how everything fits together. For my building, the 3D model made it easier to see the overall shape, height, and exterior design. However, I think 2D drawings are still necessary because they show specific details that are harder to understand in 3D. For example, my floor plans make it much easier to see how the rooms, hallways, and staircases are arranged. Contractors and engineers still need these drawings because they provide a clearer reference for dimensions, layouts, and construction details.
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.
Schedules can be useful because they automatically organize information from the Revit model, which can help estimate quantities and costs for construction. For my project, I used the Gross Floor Area (GFA) provided by Revit to better understand the total size of my building. One thing I realized is that the total square footage doesn't necessarily tell you how much usable space there is. Some of that area is taken up by hallways, stairs, bathrooms, and mechanical spaces. I also think it's important to double-check schedules because even if Revit is accurately reporting what's in the model, that doesn't mean the model itself is completely correct.
◦ 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? Version history is especially important when multiple people are working on the same model because everyone needs to know which version is current. If someone is working from an older version, they could end up making decisions based on information that has already changed. For my project, I published different versions as I updated my drawing sheets and title blocks. If a consultant told me they used last week's version, I would need to know exactly which version they used, what changed since then, and whether those changes affect their work. I think a model should be formally issued when it's ready for other people to rely on, rather than every time someone makes a small change and saves it.
◦ 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?