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?

◦  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.

Answer: 3D is best for the overall form, how the U shape sits on the site, how the podium and the wood floors stack, and for showing a client what the courtyard and the units will feel like. 2D is still needed for anything someone has to measure, price, approve or build from. The contractor needs dimensioned plans and sections, the code official needs plans with egress paths, room names and areas, and the fabricator needs exact sizes. That has not gone away, because a drawing is a fixed, signed record at a scale you can measure, and a 3D view changes depending on where you orbit. An example in my building is the wall assembly. A 3D view shows a wall, but it cannot show that the upper walls are wood studs with mineral wool and fiber cement while the podium is concrete with XPS, or how thick each layer is. You need a section and a layer list for that.

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.

◦  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?

Answer: Schedules can support procurement because the door and window counts, types and sizes come straight from the model, so a supplier can price them and the team can order the right number. For model based estimating, room areas and wall and floor quantities can be multiplied by unit costs, and when the design changes the numbers update on their own. The danger is a schedule that is accurate about the model but wrong about the building. If a room is not enclosed, or a window was modeled as a generic type, or a unit is missing a door, the schedule will still report it like it is right. It only knows what I modeled, not what will be built. My calculated field (% of Total Unit Area) showed me something I would not have guessed from the plans. The 12 studios are 14% of the units but only 8% of the unit area, and the 2 Beds and 3 Beds together take up 57% of the residential floor area. It also made it obvious that corridors, stairs and the elevator add up to about 10,400 SF that nobody can rent.

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?

Answer: Version history matters more on a shared model because other people are making decisions off it. The structural, mechanical and plumbing engineers in Weeks 6 to 8 will work from what I publish, so if I change a room or a wall and nobody can see what changed or when, they could be designing around something that no longer exists. On a personal model I am the only one who has to remember. If a consultant says their work was based on last week's version, I need to be able to tell them exactly which version that was, what changed since then, and whether the change affects their work, like a moved wall, a new fixture or a different ceiling height. The version compare in Data Management is what lets me answer that. A model should be formally issued, not just saved, whenever someone outside me will rely on it: a milestone review, a hand off to a consultant, a permit or pricing set. Saving is just for me, but issuing means other people can rely on it.