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.
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 information shown at a particular location should depend on who is viewing it and what they need to know. A client would likely prefer a simple 3D view that shows the appearance, layout, and overall design of a space. A contractor would need dimensions, material information, and construction details to build it correctly. A code official would focus on aspects such as egress routes, accessibility, and fire safety requirements, while a fabricator would need exact dimensions, material specifications, and connection details to manufacture components.
Showing everyone the same view could overwhelm people with unnecessary information. It could also make it harder for them to find relevant information, causing them to miss it. The increased overall confusion would likely lead to costly mistakes both financially and time-wise. Filtering the information for each audience makes the model easier to understand and more efficient.
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?
Schedules can support procurement and model-based estimating by automatically organizing information such as the quantities, sizes, types, and areas of building components. This makes it easier to estimate material costs, determine how many components need to be ordered, and update quantities when the design changes.
However, a schedule can be accurate based on the model while still being wrong about the actual building if the model contains incorrect information, missing elements, or components that have not been updated to reflect the final design. For example, my door schedule initially did not include the elevator doors because they were categorized as specialty equipment instead of doors. I had to manually address this issue to make sure the schedule accounted for them. It is also possible that design decisions are made during the project but never updated in the model, causing the schedule to reflect outdated information. This shows why it is important to check both the model and the schedule rather than assuming that automatically generated information is always correct. For example, an error in the schedule could cause people to order incorrect amounts or types of material, which can cost a lot of extra time and money.
Calculated fields can also reveal information that is not immediately obvious from the plans. By combining existing information from the model, new and useful information can be derived. My calculated field was occupancy, which is an important factor in building design and code approval. Although the model contained the information needed to calculate it, occupancy was not automatically provided.
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 is especially important in a shared model because multiple people may be making changes at the same time, and different team members may be relying on different versions of the building design. Without clear version tracking, it can be difficult to determine which changes were made, when they occurred, or who made the change so they can be asked questions. On a personal model, version history can be helpful for work recovery but is less risky since the person would know what chnages thay made.
If a consultant says their work was based on last week's version, I would need to identify the exact version they used, compare it with the current version, and determine whether any changes made affect their work. If yes, I should be able to list out these changes and make suggestions accordingly.
A model should be formally issued when it has been reviewed and is ready to be used for the next phase of project. Simply saving a model does not mean it is ready for others to rely on since it could still be a draft. Formal issuance establishes which version is authoritative, what it is intended to be used for, and when it was released, helping reduce confusion and prevent people from building or making decisions based on outdated information. It could also be important to formally notify people if you made a change that could fundamentally change their work.