Module 5 - Points to Ponder

Submitted For
Module 5 - Points to Ponder
💡
Please share your comments on 3 of the following 5 questions.

Which building information is best conveyed in 3D, and which still requires 2D?

3D views are more useful for understanding the aesthetics of a building, including how different elements look together and how materials and finishes affect the overall appearance. On the other hand, 2D drawings are more useful for the actual detailing of the building, as they allow dimensions, elevations, construction details, and the relationships between individual elements to be shown more precisely.

For this reason, all stakeholders still need 2D drawings! While 3D views help communicate what the building should look like, the precision of 2D drawings are more useful for constructability, communication and accurate decision and design.

One example is the connection between walls and floor slabs, which can be difficult to see clearly in 3D because of perspective and overlapping elements. Elevations and sections are much more useful for this, as they provide clearer views of how elements align, connect, and relate to different building levels.

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 organize model elements and materials into quantities, making it easier to understand what is included in the building. This is useful for estimating costs, figuring out how much material is needed, and planning where to purchase different components. The information can also be used for further calculations to better understand the design.

Schedules depend on the information in the model. Therefore, if something is missing, incorrect, or simplified, the schedule will reflect that rather than what the building actually needs. This is especially important when parts of the design are not fully developed, as the numbers may appear accurate even though they don't represent the final building.

One schedule parameter that was particularly interesting was occupancy. The occupancy calculations were useful for comparing rooms across different floors and between the two buildings, since their layouts are not always the same. While the floor plans show the sizes and arrangements of spaces, the occupancy values made it easier to check whether similar rooms were sized appropriately and identify any differences that might need another look.

You published two versions and compared them.

In a shared model, multiple people may be working on different parts of the project at the same time. Version history helps everyone keep track of changes, know which information is up to date, and access earlier versions when needed.

If a consultant says their work was based on last week's version, I would need to know how many versions of the model have been created since then and what changes were made in each. More importantly, I would need to identify exactly what has changed since last week, particularly anything that could affect the consultant's work. This would help determine whether their work is still accurate or if anything needs to be updated to match the current model.

In general, a model should be formally issued when it reaches a clear project milestone or is ready to be shared for a specific purpose. Each issued version should have a clear reason for existing, making it easy to understand what has changed and how it differs from previous versions.