Weekly Inspiration

I found this image of a bridge-like design and complex that's very similar to my site and current ideas for development- high rises on one side, an aquatic depression, and a bridging structure to traverse it. I'm hoping this will keep me inspired for next week's iterations!

Floor Plans

Here are my floor plans for this week where I have worked out the first iteration of program organization and building layout.

The general concept is that this is a "working" library, less for access to materials, and more for areas to work, meet, and collaborate. Limited material will be available for "browsing" and will be organized by topic (similar to a bookstore) than by traditional library systems, such as the Dewey Decimal system. The work areas get quieter as you ascend upward. The upper-most floor is a mezzanine level for library staff offices.

Circulation areas and "movement" areas will contain loose book stacks that people will be forced to walk passed and "browse" as they move to their desired location within the building.

I have axons and sections of the building, but can't post them yet because I need to scan them...I will get them up here ASAP.

On networks and circulation patterns

Paul Baran, On Distributed Communications Networks, RAND Corporation, 1962

This post is a small continuation of the presentation on networks and circulation. By identifying the different types of networks one can imagine new ways of organizational principles in architecture. That can be applied either as an organizational diagram of program or as an internal/external circulation system. Each of the different network systems, as presented by Baran, have got both advantages and disadvantages for communications regarding effectiveness and alternative routes. Borrowing elements of these concepts from fields outside of architecture can spark ideas on how one can be more inventive with the way the users of a building can move around on their way to a certain part of it, how long that might take, how many options they might have to reach the same point from alternative routes and so on.
__


Paul Baran (1926–2011) was a Polish American engineer who was a pioneer in the development of computer networks. He worked for the computer science department in the mathematics division of the RAND Corporation, a nonprofit research and development organization funded mostly by government grants. At that time the RAND Corporation focused mostly on Cold War-related military problems. Baran thought he could design a more robust communications networks using digital computers and by introducing redundancy.


At that time there were two basic models for building communication networks: centralized and decentralized. In a centralized network all nodes are connected directly and only to a centralized hub or switch. All data is sent from an individual node to the center and then routed to its destination. If the center is destroyed or not functioning all communication is effectively cut off. If the route between a node and the center is destroyed or not functioning, that node is effectively cut off. A decentralized network uses several centralized hubs. It is almost like several small centralized networks joined together. Each individual node is still dependent upon the proper functioning of its hub and the route to it.


Baran suggested a third alternative—a distributed network—"a communication network which will allow several hundred major communications stations to talk with one another after an enemy attack. " (Baran, Rand Memorandum 3420-PR, CH.1) A distributed network would have no centralized switch. Each node would be connected to several of its neighboring nodes in a sort of lattice-like configuration. Therefore, each node would have several possible routes to send data. If one route or neighboring node was destroyed, another path would be available.


Excerpts via: ibiblio