This WRNS Studio model is a frequent image these student bring to class to ask about integration issues.
I team-teach Project Integration Studio. By mid-semester, these students model structure, ducts, and lights to be integrated harmoniously with the floors, walls, and ceilings of their (otherwise) typical studio projects.
That’s a lot for an architecture student fresh out of Design II. That’s why the studio fosters teams of three or four students per project.
Teamwork is hard. Miscommunication is costly in a group. But, each year, the students arrive with more robust modeling abilities. Each year, they are quicker to get it all in the computer.
That’s why it is a pleasure to walk through the school computer labs and quietly listen to these teams work through their problems. They point to the model. They generate new views to visualize the issue. They talk spatially.
I tell my students “It is a fantastic time to become and architect.” because of these new tools. Those with sharper ears probably see the other meaning: “Its a fantastic time to be architecture professor.”
One of many proposals for expanding 3D Printer facilities…
The Institute may invest in more desktop 3D Printers one day soon. Where should we put them?
When considering our Fabrication Lab, recent conversation turned to how the folks at the Makerbot store have done something quite skillful. They use a handful of inexpensive desktop printers to create an atmosphere of progress, experimentation, & technological ease.
The stores specifically get visitors excited about technology by addressing both their eyes and their ears. Read more
The Element table started in E-202, and has migrated to the G-202, and well beyond…
Defining roles on a team is of primary concern at any project Kick-off Meeting. It’s all the more important as BIM-capable teams try integrated delivery techniques.
The structure and form of the AIA E-202 (2008) was the AIA’s first exhibit in its suite of legal instruments to help architects define BIM Manager roles on any team attempting an integrated workflow. On many of the teams I work with, that document was largely considered incomplete. It might sketch modeling expectations, but it was a poor tool to answer detailed questions about who-delivers-what-when. Read more