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?
All stakeholders need 2D drawings because they are simple and accessible to all stakeholders: construction, design, and manufacturers all have 2D drawings as the industry standard. When considering that 3D models are not ideal for people who aren’t tech-savvy, 2D models are a great resource for the deliverability of ideas.
◦ Give an example of something in your building a 3D view fails to communicate.
A 3D view fails to communicate the maintenance accessibility needed for some aspects of the space. When designing, one will have dimensions for space, but it will not be clear that once these forms are constructed, those dimensions are not accessible for a technician to work on.
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?
For a client, a general overview of the 3D site and general floor plans and processing are the most useful. The client needs to be kept in the loop with what is going on and important design decisions, but it is not necessarily needed to give certain technical views that the client may not have the background to understand or the expertise needed to make a design decision without them.
For a contractor and code official, information will be filtered based on building materials, schedules, and key structural information such as beams and railings that are required for building codes. For a fabricator, a 3D view and furnished unit plan may be more useful.
◦ What is the risk of showing everyone the same view?
The risk of showing everyone the same view is the possibility of providing the wrong information that will not allow different stakeholders to make guided decisions. The information that a contractor needs to assess the design and build is different from what a fabricator would need.
If different views are not offered, the scope of what is being collaborated on is also limited. The more views, the more information is being facilitated within the group. This allows for any possibility: from potential designs to possible failures to be vetted by different people on the team.
View templates enforce consistency across a set.
◦ What goes wrong on a real project when views are configured individually?
When views are configured individually, they run the risk of presenting a view of the design that is misleading. It becomes the “one truth” of the design, when one view alone can easily miss key information that could only be understood from different views of the same build.
◦ Who should own the templates and standards, and why?
A centralized team, because it protects the designs from being altered in ways that jeopardize the various aspects of the build that are being designed by different stakeholders on the team, ensuring accountability.