As we wound down our a charrette, an exercise somewhere between a Top Chef “quick fire” and a game of “exquisite corpse,” we remembered seeing flickering pixels, oversized movable louvers, folding organ-like planes, and stretching ribbons. Our research yielded a number of innovative precedents —both theoretical and built— from architects and engineers experimenting with movable facades around the world. We had examined automated fins and shading umbrellas, tessellated screens and adaptive fritting from ABI, the homeostatic façades from Decker Yeadon, and the Aegis Hyposurface from Goulthorpe, among others.
But it was not enough that these façade components moved, either by means of carefully controlled computerized programming or by more rudimentary manual, hydraulic, or mechanical means. The movement that we were trying to describe was different. It had to be tied to performance. It had to respond to the sun. As Mike Hickok often said, it had to behave “more like a plant, less like a machine.” With our newly acquired understanding, how could we propose a future in which shading devices would deploy and contract biomimetically, like the artificial muscles we studied, in response to the sun?
Then we had a rude awakening. How could we even begin to tinker with these shapes with our limited experience, with the kind of software that had the capabilities to produce what we needed? Clearly we had found ourselves at the convergence of technology, media, and representation. We needed to make leaps in all three. As Lisa Iwamoto describes on her book Digital Fabrications[i], our design had to inform and be informed by its modes of representation and production. We had to go beyond, way beyond, the limitations of what we traditionally produced in-house and do it at the fast pace of a design competition. At once we were dealing with modeling software shortcomings, researching smart materials, studying artificial muscles, defining performance, contracting out the scripting of algorithms, buying software, and storyboarding the presentation to determine deliverables and staff allocation.

Rhino image of ribbon
Mike Fischer[ii], a fifth young designer was brought on board, contracted to work side by side with our team to help with computational modeling and scripting. We shifted to Rhino, a NURBS-based modeling software that would allow us to conceptualize, tinker, and control our shading strands. While developing the component, we needed to test it across the façade. Mapping it and remapping it to control its size, density, and openness required formulas—a lot of formulas—which we crunched in Grasshopper.

Read more
Categories:
A New Way of Designing,
Architects,
Business,
Craftsmanship,
Design,
Ecomimicry,
Research,
Science,
Smart/Intelligent,
Systems,
Technology