SQM: The Quantified Home, (2014). Edited by Space Caviar

Note: an interesting project /book by Space Caviar about the “house” under the pressure of “multiple of forces - financial, environmental, technological, geopolitical -”, to read in the frame of I&IC. Through its title, the book obviously address the question of domesticity immersed into technologies and the monitoring of its data.

While our project is gravitating around “networked objects/spaces”, the question of their monitoring, so as the production or use of data (“pushed” into to the cloud?) immediately comes into question, of course.

In this context, we must also point out Google and Apple efforts to tap into the “quantified house” with Nest and Homekit.

 

Via Space Caviar

—–

 

The way we live is rapidly changing under pressure from multiple forces—financial, environmental, technological, geopolitical. What we used to call home may not even exist anymore, having transmuted into a financial commodity measured in square meters, or sqm. Yet, domesticity ceased long ago to be central in the architectural agenda; this project aims to launch a new discussion on the present and the future of the home.

SQM: The Quantified Home, produced for the 2014 Biennale Interieur, charts the scale of this change using data, fiction, and a critical selection of homes and their interiors—from Osama bin Laden’s compound to apartment living in the age of Airbnb.

With original texts by: Rahel Aima, Aristide Antonas, Gabrielle Brainard and Jacob Reidel, Keller Easterling, Ignacio González Galán, Joseph Grima, Hilde Heynen, Dan Hill, Sam Jacob, Alexandra Lange, Justin McGuirk, Joanne McNeil, Alessandro Mendini, Jonathan Olivares, Marina Otero Verzier, Beatriz Preciado, Anna Puigjaner, Catharine Rossi, Andreas Ruby, Malkit Shoshan, and Bruce Sterling.

The book is published by Lars Müller, and will be available for sale worldwide from November 2014. The dust jacket is screen-printed on wallpaper in 22 different patterns, randomly mixed.

 

Download the table of contents

I&IC Workshop #2 with James Auger at HEAD: Design Implications

Based on the concepts and scenarios produced in our second workshop, we decided to work on the design implications of such projects. More specifically, we realized the set of contexts (religion, music, etc.) the workshop participants worked on share common traits: the needs for a cloud infrastructure was fairly similar and let to the idea of a basic “data unit”. Such a mobile system would act as a mini-data center.

data-unit

To some extent, it’s similar to Pogoplug, but it would be more tightly related to the context of use and inserted into specific artifacts and devices at home, our on the street; as represented on the following pictures:
dataunit-piano-01
dataunit-banc-01
datauinit---cabine-tel-01

The idea here is that this normalized version of the data unit can serve an almost-visible infrastructure : inside a church bench, a phone booth or a musical instrument.

I&IC Workshop #2 with James Auger at HEAD: output > “Cloudified” Scenarios

Note: the post I&IC Workshop #2 with James Auger at HEAD, brief: “Cloudy” presents the objectives and brief for this workshop.

 

After last week’s workshop at HEAD – Genève, we learnt that addressing Cloud Computing from a design perspective requires to take a detour. Instead of looking at data centers and cloud computing directly, we asked students to choose a domain of everyday life (religion, cooking, communication, etc.) and work on how this technology may influence it, the kinds of practices that may emerge and what kind of implications would surface. The projects reflect this diversity and we also push the student to adopt both a critical and speculative angle. Such requirements mean that the output of the workshop largely consists in a set of short scenarios/usage strategies exemplified by sketches and pictures. Each of them provides a subtle perspective on cloud computing by showing that the limits and the opportunities of these technologies are entangled.

 

Cloudified Scenarios – a workshop with James Auger at HEAD – Genève on Vimeo.

 

Two posts have been added later as follow-ups to this one that propose an update to the direct results of the workshop:

- http://www.iiclouds.org/20141112/iic-workshop-2-at-head-design-implications/

- http://www.iiclouds.org/20141112/iic-workshop-2-at-head-ui-proposals/

 

bigMother (Camille Rattoni & Sarah Bourquin)

The project revolves around the idea of a cloud-based sharing and assistive system to help citizens dealing with the everyday duty to cook at home. More specifically, it addresses the activities around cooking logistics such the organization to access qualitative food supplies, or the access to relevant recipes. Citizen cooking and consumption habits are automatically stored in each instance of bigMother. This system was felt as intrusive by the local communities but they understood that their data can be used to optimize the access to qualitative food products and avoid wasting resources. Based on this analysis a set of cloud services enable people to choose recipes based on product availability and health issues (intolerances, family disease, etc.)

 

Neighborhood instances

 

 

Moreover, bigMother’s cloud system is designed to be used at the neighbourhood levels of a city/small town (5’000 to 10’000 inhabitants). In this case, the cloud is not meant to be global platform but it is grounded physically at the local level. This means that big urban areas would have several bigMother “instances”, unaccessible from people who do not belong to these communities (in order to limit the potential privacy intrusion/data leaks). At the kitchen level, each appliance (fridge, boiler, oven, bread machine) are also connected to bigMother cloud in order to collect data and synchronize their suggestions.

The project highlights the difficulty in finding a proper balance between health/sustainability issues and data collection/intrusion needed to optimize people’s cooking habits. The name of the project also reflects the fact that surveillance can also happen at the local level (within neighborhood communities).

-

CATHEDRAL (Léa Thévenot & Etienne Ndiaye)

Religion is an aspect of everyday life that does not always correspond to the general public’s perspective on technology. But, as this project implies, there are interesting connections between the two. CATHEDRAL is a scenario that envision the role of cloud computing technologies in the context of Christian faith. It investigates religion in an era where churches are getting more and more empty and faith is seen as part of the private sphere.

 

CATHEDRAL-UNISON

 

 

The design proposal consists in a series of glass bells called “unison”. They draw inspiration from architectural elements we find in religious buildings.Their symbolic purpose is to bridge the geographical gap between believers and to unite them behind a domestic monument. These bells act as resonators (echoic chambers) for a sound to be amplified, but also as light diffusers. Every bell has a different shape, and thus a different behaviour with sound and light. The unison bell are also characterized by two modes:

  • A passive mode to support the realtime broadcasting of prayers said around the world by people using this device. For the user, the sound is heard as a form of ambient non-intrusive music.
  • An active mode in which the user can say his/her prayer and hear the prayers uttered by other believes simultaneously as a background audio track. At the end of the prayer, the bells reproduce in unison all the version of this prayer uploaded to the cloud in a kind of spiritual sonic mass.

-

MOODIANO (Patrick Donaldson, Eunni Sun Lee, Saskia Vellas)

This scenario explores how a musical instrument (a piano) can be connected to the cloud and collect data about its usage. It is based on the assumption that there is a correlation between music playing and emotions, and that it would be possible to map people’s emotions based on this kind of information. Each piano is defined by its geolocation as well as a mix of data (notes and chords played, keys, musical genre, pressure, speed/rhythm) and metadata (weather, time of the day, etc.). Based on collecting these information, it is then possible to envision an interface to visualize piano usage. Such representations would correspond to mapping of players’ mood.

The group described how third parties – politicians, commercial companies, etc. – may use this information to inform their decision. For instance, public institutions may wonder how the population’s mood, represented by these data, can help then wonder if it is the best moment to pass a new law/tax.

 

Moodiano

 

This project revisits the notion of Smart City by showing how collected data can be helpful in a decision-making process. To some extent,one can see it as a revamped version of Cybersyn – a distributed decision support system to aid in the management of the national economy in Chile in the 1970s – based on data-analysis of piano usage. Using this, a musical instrument becomes a tool to understand populations.

-

L’Oracle (Hind Chamas, Alexandra Gavrilova, Vanesa Lorenzo)

Oracles have always played an important role in society. In the Greek Antiquity, they predicted certain events, based on a form of divination or anticipation. This groupe revisited this notion in the context of cloud computing. Their assumption was that data collected on online services, mobile devices and any piece of technology could help generating predictions and/or recommendation in a way that is similar to Oracles. They envisioned an interface located in phone booths that would perform facial and speech recognition on a user, analyse existing data about him/her (social profile, personal data, family connections, religion, contacts, etc.) and provide the person with an answer.

However, in order to go beyond the standard utilitarian perspective of decision-making interfaces based, the group chose to explore how to poetize everyday experiences and promote another form of recommendation based of literature references. The user would go to the booth, ask a question and the answer would be given in the form of a piece of poetry.

 

Oracle

 

In this case, the cloud computing system corresponds to a public database of personal data with a set of tools to analyze the questions and confront it to contextual information (weather, facial emotions, voice timber, etc.), recognize the language employed by the user and tap into a pool of poetic references in order to find an adequate reference. The intelligence in the system lays in this answer which will be mysterious at first and then evocative for the user… in the same way Oracle’s prediction and advices were.

-

WHERE THE WILD THINGS ARE (Mélissa Pisler & Marianna Czwodjdrak)

This project explored the relationships between cloud computing, sensors and animals. It focused on how animals can play a role in environmental monitoring. The group started from the idea that rats may suffer from cardiac remodelling and ventricular arrhythmia that can lead to heart failure, because of CO pollution. This means that rats can act as “canaries in a coal mine” to detect such pollution (an idea already explored by Beatriz da Costa in her Pigeon blog project).

 

Cloud rats

 

The point here is to have sensors wore (or ingested) by rats in order to map out pollution, and benefit from their pervasive nature in urban environments. The rodents could easily gather information, using mesh network technology which may also provide a way to store such data, and eventually form a distributed cloud system.

-

Smart Personal Cloud (Charles Chalas & Félicien Goguey)

The last project addressed the notion of smart personal cloud and ambient information. It’s based on a wearable device that helps user going through his/her work of the day, logging every event in real time. The data recorded is uploaded to the cloud, where an artificial intelligence will analyze it, tag it and sort it, to finally archive it for further use. The AI will then use this data to assume the role of a personal assistant, reminding the user of various tasks and to-dos, providing useful and highly personalized information about who or what you encounter. It will also be there to coach people into being more productive, squeezing up to the last bit of work potential out of every moment.

-

Acknowledgements:
Thanks James Auger for the workshop mentoring; Charles Chalas for his help preparing the workshop week and his participation with Félicien Goguey (MD2); Patrick Keller, Christophe Guignard and Lucien Langton for the participation to the final crit. Thanks the Media Design students (MD1) from HEAD – Genève for the enthusiasm, their involvement and their projects: Camille Rattoni, Sarah Bourquin, Léa Thévenot, Etienne Ndiaye, Patrick Donaldson, Eunni Sun Lee, Saskia Vellas, Hind Chamas, Alexandra Gavrilova, Vanesa Lorenzo, Mélissa Pisler, Marianna Czwodjdrak.

I&IC Workshop #2 with James Auger at HEAD: ongoing work

Workshop day 2, we’re working on the various contexts in which cloud computing and data centers can be deployed in the near future. Each group started exploring domains such as religious objects/ambiance, local communities, illegal content smuggling, urban animals and music playing.

 

James-diagram

discussion

Diagram-wkshop1

Etienne-prototyping

I&IC Workshop #2 with James Auger at HEAD, brief: “Cloudy”

At HEAD – Genève today, we started the first workshop of the research project with James Auger (from Auger-Loizeau design studio and the Royal College of Arts in London). We’re going to spend this week with the first year students of the Media Design MA exploring cloud computing, personal cloud systems, objects and user interfaces.

In order to address this, the workshop started with a background description of the project’s purposes, the evolution of computers and network infrastructures, as well as an introduction to the current state of design objects and architectures related to cloud Computing: NAS systems, servers combined with heater, speculative projects related to such technologies. From this broad list of material we wondered about the lack of artefacts that go beyond purely functionalists goals. Cloud computing systems, especially in the context of people’s context is generally a commodity… hence a need for design interventions to re-open this black box.

Following Eames’ quote “A plan for arranging elements to accomplish a particular purpose” (as a definition of design), we asked students to start with a basic activity: to create a map of “elements” related to cloud computing. They had to choose a domain of everyday life (cooking, communication, etc.), begin by compiling “their” elements (material scale, cultural, historical, list people’s motivations, objects used to achieve it, situations, behaviors, etc.), sub-themes.

From this we discussed this ecology of elements and what aspects or user contexts they could focus on. Interestingly, students chose very broad topics: religion, communication, cooking, art performances, animal-computer relationships or music-making.   Based on this map, we then asked students to explore the role of cloud computing into these elements by looking at these questions:

  • How elements of the diagram might work with the cloud? How the cloud may influence each of these elements/the relationships between two of these elements?
  • How relationships between the elements on these maps may evolve with cloud computing?
  • What are the new situations/problems that may arise with the cloud? Implications?
  • What kind of objects will be linked to the cloud? Why? (From products to the role of the product and situations that arise)

The (many) answers to these questions led the groups to highlighting design opportunities to be discussed tomorrow.

Toward OwnCloud Core Processing Library

The purpose of the OwnCloud Core Processing Library is to give the possibility to program “cloud functionalities” within a well known and simplified designer oriented programming language (and community): Processing.

 

Therefore, the OwnCloud Core Processing Library linked with our personal cloud merges the Open Collaboration Service (OCS) Share API with higher level functions in order to implement seamlessly “search&share files” applications written in the well known designers oriented Processing programming language. This will soon become available to everyone on the I&IC website. The workshops we are currently running / will run during the coming weeks are helping/will help us fine tune its functionalities.

 

The OwnCloud Core Processing Library allows the automation of the action of sharing files and the action of file tagging within an open source OwnCloud environment. Search&Sharing tasks can be threaded and/or interdependent, everything depending on the kind of results expected from one application to another. Thus, these actions can be driven by unmanned processes, decision-making (copy, delete, share one or several files) based on related metadata (i.e. metadata relation/link) or based on external data, dug from the Internet or networked/connected items/things.

 

Basically, the core library needs to identify an OwnCloud server, with a set of valid credentials. The application using the OwnCloud Core Processing Library is then able to manipulate files, download, upload, duplicate or move them server-side (without downloading the files on a local computer). It is as well possible to share files with another user or group of users on the same OwnCloud server. Depending on the application, several connections to several distinct OwnCloud servers can be managed, making possible to transfer files from one OwnCloud server to another (network of servers).

Metadata associated to files work on a key->value pair basis (i.e. ‘date->10/12/1815′, ‘city->London’, etc…). Any number of metadata can be defined for every single file. While duplicating a file, one can decide if attached metadata should be replicated as well or not (i.e. the duplicated file can already be associated with the same metadata set as the original one (inherited metadata or not). The core library allows to retrieve all metadata for a given file or to perform a search through metadata in order to obtain a list of files having the allowed metadata set with the desired value(s). This particular set of functions is part of the higher level functions proposed by the OwnCloud Core Processing Library, above the OCS Share API.

 

The core library is JAVA based (using WebDav JAVA implementation library Sardine). A connection to the Processing framework has been implemented, making the OwnCloud Core Processing Library available within Processing.

Setting up our own (small size) personal cloud infrastructure. Part #2, components

While setting up our own small size data center and cloud infrastructure, we’ve tried to exemplify the key constitutive ingredients of this type of computing infrastructure, as of November 2014. But we’ve also tried to maintain them as much open as we could, for further questioning, developments and transformations.

The first key ingredients are software parts and we’ve described them in the previous post about the same topic.

iic_server_03s

The other key ingredients that we’ve used to set up our “data center” are the normative approach of the U and the mobile 19″ rack cabinet. The idea of redundancy of both hardware (RAID disks) and data is fundamental too, which is extended further with the doubling of electric and internet access plugs (in a big size data center, these redundant plugs are connected to redundant sources, in case of failure in the energy or network access supply chain. And if both energy sources fall down, two local powerful oil engines are ready to take over). We also maintained the need to monitor temperature and air flow in an autonomous manner.

 

IMG_3846m

At a small scale, our “data center” has a false floor and ceiling, it maintain enough free space for cables and plugs around the computing unit itself. Fresh air comes from the ground, while hot air charged in positive ions goes out of the cabinet from the top.

-

Please see also the following related posts:

Setting up our own (small size) personal cloud infrastructure. Part #1, components

Setting up our own (small size) personal cloud infrastructure. Part #3, components