atom01 talk:Home

From student
Revision as of 12:21, 12 September 2011 by Lieke (Talk | contribs)
Jump to: navigation, search

atom01 talk


WEEK 01

First Meeting

Before the first meeting took place Atom 2 visited the site and made a atom02:map of the site and its surroundings.For the first meeting we created a presentation slide to present our concerns for the site and our interests within the design field. This slide can be seen here.


Site Analysis

Analysis gave us the following reasons why people hardly visit the site:

- The site has no program

- There is no landscaping or landscaping attributes (e.g. lamps, benches)

- The lush green border around the site works like a fence during summer

- Very diverse programming around site, site is leftover space.


Conclusion of analysis:

People don’t use the site, because there is no reason created to use it. Since people don’t use the site it is deserted, giving people passing by an ‘unsafe’ feeling (there is nobody there to control or watch over)


Goal for the site:

To create a building that offers divers programming 24/7. (Never a ‘dead’ moment)


Design Goal

How can a building support activity 24/7 ?

A website works 24/7 (ignoring maintenance) and is continuously evolving; e.g. a wiki page; the user is free to add content and to make it public worldwide. This way of doing things might inform our architecture in the sense that the physical site will deliver and permit a widespread of activities, programmable via a public website (multiple bookings will be possible if within the limitations of the program; I’m using program here to refer to the actual algorithm and physical site). Thus the site will be continuously changing and allowing the interweaving of human interaction (a lecture hall, next to a performance space next to individual study-rooms, etc).


Concept

The building that is to be designed will work with a 3 layer change system. Layer 1, the user creates and uses the content. Made to demand building. Layer 2, the environmental influences, the footprint of the traffic. Layer 3, evolutionary process, the small traces visitors leave behind.


Hierarchy of change:

1 | Creating a Made to Demand system the user can ‘book’ spaces in the building (eg via a website), after which the building will adapt it’s shape to the preference of the user. This means that (for example) at one point lectures could be given in the building, while at another point the building will consist of several group workplaces. The Made to Demand system has the biggest impact on the change of the building

2| The site is surrounded by some heavy traffic routes that leave a footprint on the site, eg CO2 emission, wind flows and noise. This footprint of the traffic flow will affect the building in a more superficial way (eg. creating sound barriers)

3| The user leaves his trace in a very subtle way that will become slowly more visible over time. This is part of the evolution of the building.

atom02:12th-09-2011

Personal tools
Namespaces
Variants
Actions
Projects
Atoms
Toolbox