Module 5 - Points to Ponder

Submitted For
Module 5 - Points to Ponder

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

  • 3D is best for:
    • Conveying the exterior of the building
    • Testing material changes (since you can actually see what they’ll look like)
    • Checking consistency across levels all at once.
  • 2D required for:
    • Precise information such as, dimensions, wall thicknesses, layered assemblies
    • Schedules such as windows, doors, rooms, and occupancy.

Which stakeholders need 2D drawings, and why has that not gone away?

  • Almost every stakeholder relies on 2D drawings, especially floor plans.
    • Code officials use them to verify that dimensions meet code
    • Contractors reference them during construction
    • Clients use them to confirm the layout matches what they expected and to weigh any changes
    • Designers use them to optimize the space and plan furnishings.
  • 2D hasn’t gone away because it is the easiest format to share and understand on paper or PDF, it is the standard for legal contract documents and permit submissions, and it is the most reliable way to reference exact dimensions.

Give an example of something in your building a 3D view fails to communicate.

  • In my building, a 3D view fails to communicate wall thicknesses, the number of doors leading into each room, and the layers of insulation in the walls and roof.
  • A very good example of this was when I built my roof and exterior walls layer by layer. I needed the section view to see each layer, compare its thickness to the others, and confirm that everything I intended to include was actually there.

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?

  • Take an outdoor space like my inner courtyard or a balcony.
    • Client
      • They want to see how they will use the space: visualizations of the patio or balcony, furnishings, and any features they specifically requested. They also care about performance, like energy efficiency and expected electricity costs.
    • Contractor
      • They need distances, materials, wall dimensions, and the logic of the building systems, making sure they leave space for plumbing and electrical. They are also responsible for having the right number of doors and windows and installing them in the correct places.
    • Code official
      • They focus on safety: railing heights, connections, egress and fire exits, distances, and building height.
    • Fabricator
      • Unlike the contractor, who coordinates the whole site, the fabricator needs component-level detail, such as the specific materials and dimensions for a particular door or window, down to the pane level, so each piece gets built exactly as designed.

What is the risk of showing everyone the same view?

  • A single view containing everything would be overwhelming, making it easy to miss an essential component.
  • It also increases the risk of people misinterpreting information, not understanding what an element is, or acting on information that wasn’t meant for them.

You published two versions and compared them.

Why does version history matter more on a shared model than a personal one?

  • On a team, saved versions let you recover elements that were accidentally deleted and give you a reference point when different teams debate priorities.
  • It creates accountability: if someone changes a component that isn’t assigned to them or that they shouldn’t be changing, you can catch it and see who made the change and when.
  • It lets the team compare the latest changes against previous versions to determine whether they’re actually improvements.

If a consultant says their work was based on last week's version, what do you need to be able to tell them?

  • I need to be able to tell them exactly what changed since last week’s version and which parts of their work now need to be reanalyzed.
    • They know what was in last week’s model but not the changes since then, and their analysis and conclusions could change once they’re working from current data.

When should a model be formally issued rather than just saved?

  • A model should be formally issued when other people will rely on it to make decisions, such as for permitting, bidding, construction, or a consultant’s analysis.
    • Saving is part of ongoing work, but issuing freezes a specific version with a date and label, this is beneficial because it ensures everyone knows exactly which version their work is based on.