Community Research and Development Information Service - CORDIS

H2020

OrganiCity Report Summary

Project ID: 645198
Funded under: H2020-EU.2.1.1.3.

Periodic Reporting for period 1 - OrganiCity (OrganiCity – Co-creating smart cities of the future)

Reporting period: 2015-01-01 to 2015-12-31

Summary of the context and overall objectives of the project

In its first year, the OrganiCity consortium has built the Experimentation-as-a-Service facility as planned. Based on co-creation processes in the three clusters of London, Santander and Aarhus, and with contribu-tions from the other partners, the facility has been defined and instantiated. The system architecture integrates both local systems and provides a federation and linking across sites based on the Open & Agile Smart Cities mechanisms.
Furthermore, a set of co-creation tools have been developed and made ready for the first round of experimentation: the Scenario Tool, the Urban Data Observatory, Tinkerspace, Smartphone Experimentation, Opportunistic Connectivity Service, Crowd-sourced Data Annotation and Tangible Interaction using the DUL Radio.
The open calls have been co-created with the communities in the three clusters, and the legal and support frameworks around the experimentation have been established. There is an Experiment Agreement to govern the responsibilities and rights of the experimenters using the OrganiCity facility, and there is a stakeholder landscape in and around each cluster which is ready to engage in the open call experiments. Ethics and privacy is baked into the facility and processes.
By the end of the first period, the OrganiCity Experimentation-as-a-Service facility is thus ready to use, and the consortium is preparing the first round of open calls.

Work performed from the beginning of the project to the end of the period covered by the report and main results achieved so far

2.2 Explanation of the work carried out per Work Package
2.2.1 Work Package 1 Co-Creating OrganiCity
The main objective of WP1 is to establish contact to and engage with communities in the three clusters. The communities are highly diverse and include citizens, SMEs, industry, researchers, grassroot organiza-tions, authorities, etc. Through engagements, we will co-create the OrganiCity facility with these communities communities and extract requirements for the technical development of the OrganiCity tools and facility in general. WP1 is broken down in three tasks with each their focus. T1.1 is focusing on establishing contact with communities through face-to-face engagements, social media, events, experiments, etc. The task will initially leverage from existing communities, it will make sure to establish a pipeline for future engagements, and thereby create the space for co-creating the facility. The main aim of T1.2 is to extract knowledge from the communities, and create both scenarios and technical requirements for further OrganiCity developments. T1.3 is about developing an architectural vision and technical guidelines for the OrganiCity facility. The vision and guidelines will feed into WP2 and WP3 and inform the development process.
WP1 is on track, and we are currently following the schedule. Through the amendment phase, we have chosen to prolong the task according to the overall timeline, and to include a direct engagement with ex-perimenters when they are conducting and developing their experiments.
Task 1.1 OrganiCitizens : Task 1.1 was launched with efforts to better understand the communities of potential “OrganiCitizens” that are located in the three cluster cities and beyond. We started out with a mapping exercise – an internal survey across the consortium partners, calling for input on the communities whom partner organisations had previously engaged with or whom were known for their thorough experience in citizen engagement activities. In total, 24 communities were identified and categorised (Tech/Data, City Gov., Service Creation/Delivery, Enterprise and Citizen/Community/Research). The next step was to conduct qualitative research interviews with a selection of these communities across the clusters. Ten interviews were conducted by video conference and many insights were gained alongside key contrasts between the different cities involved. This research was then synthesized into seven design principles for engagement to be implemented across all OrganiCities and linked to the learnings from our adjacent communities. Deliverable 1.1 “We are All OrganiCitizens” captures this process and the design principles. It also includes the broader “engagement journey” for “experimentation-as-a-service”. This engagement journey was designed based on our qualitative research and upon leading commercial and government engagement strategies for co-creation. In addition, this task included the development of a social media engagement strategy and an analysis of the online presence and channels that should be used in the project. This engagement journey and initial social media activities is built on further in WP6 throughout the lifetime of OrganiCity.
Task 1.1 built thus on an “engagement journey”, conducted through a wide range of citizen engagement activities which has the objective to support the transition from discussion to co-creation to experimentation. The citizen engagement activities have consisted of workshops, speaking engagements, online discussions, and attendance and promotion of OrganiCity at hackathons and other public events. These activities also support the activity within communities of defining use cases, which has commenced in task 1.2.
Moving forward, we will intensify these engagement efforts as part of the announcement of the first OrganiCity open call (executed by WP5). We will continue to use our established channels to keep the communities informed on opportunities to engage with OrganiCity. The results of the first open call will guide us to iterate the strategy and our dissemination plan towards the second OrganiCity open call. At that point, we will widen the reach of our audience and grow awareness across other networks by showcasing the results of the experiments during the first open call and the experiences of the experimenters.
Task 1.2 OrganiCitizen use cases and derivation of requirements
In T1.2, we have engaged with a variety of communities over the last year. These engagements have hap-pened in all clusters, and span activities such as workshops, hackathons, meetups, social media initiatives, and presentation events. Additionally, we have established a methodology for collecting knowledge from communities. In particular, we have chosen to use what we call “scenarios” as knowledge base. From each community engagement, the aim is to generate scenarios that capture knowledge gained from the specific engagement. In T1.2 we intend to make that knowledge publicly available, and have, for this purpose, developed the so-called “scenario tool”. The scenario tool is a website (scenarios.organicity.eu - not fully publicly available yet), which will go live when the first open call is announced. We have used many efforts on developing version one of the tool, and we have currently 129 scenarios (as of February 23, 2016). This is a tangible preliminary outcome of WP1, and it has been agreed that the tool will be closely connected to WP5 activities.
The next steps in T1.2 are to wrap up the scenario tool in a version 1. We are currently working on refining how to evaluate scenarios. Additionally, we are setting up a support team for fixing bugs when end-users start to use the tool actively. We are gearing up to being active community engagers when the open calls starts up. The aim is to support experimenters actively through providing support for the OrganiCity facility, and the different tools that are being developed in OrganiCity. Furthermore, we aim for direct engagements, where we can support experimenters by developing generic tools that can be used directly in the experiments. Through these engagements, the main aim is to provide strong feedback to the developments of the OrganiCity facility. Finally, we are going to further develop the methodology for extracting functional and non-functional requirements from community engagements and scenarios, and feed them into the pool of requirements driving WP2 and WP3.
Task 1.3 Develop an architecture and implementation guidelines
In task T1.3, we build upon the scenarios and general requirements derived in T1.1 and T1.2 to provide a first high-level design for the architecture of the OrganiCity facility. The foundation of the facility is provid-ed by three cities, Aarhus, London and Santander, which are being integrated into the overall OrganiCity facility. We reviewed and investigated the main assets corresponding to these three sites. The main characteristics of such assets are, in the case of Aarhus, an open data framework that allows access to different city information such as environmental, demographic or traffic. In the case of London an IoT deployment, as well as historical and real time data, are provided. Finally, for the case of Santander a massive IoT dedeployment (inherited from the SmartSantander project) as well as real time and historical data are made available. These assets are being exposed via a number of tools and frameworks, from open data repositories like CKAN instances to FIWARE enablers, such as the Orion Context Broker for exposing live data. In the case of London a proprietary data platform is being used that provides a REST API to access and query real time and historical data end points from IoT devices and several open data instances and APIs. Aarhus integrates such data directly into CKAN. Our initial approach was to treat the federation of static open data platforms and IoT middleware separately across the three different city instances. At the second year of the project, a more integrated approach for all data sources will be investigated.
The OrganiCity facility aims to augment the assets provided by the three sites with a set of co-creation tools for collaborative city making. These tools are not developed from scratch but leverage existing ones of project partners as starting points in WP3. Among them, the mobile experimentation tool aims at supporting third party experimentation on top of nomadic and ubiquitous devices such as smartphones or tablets. In addition, the opportunistic network relay building block provides the possibility to either experiment or collect static sensor data and then relay it in an opportunistic way as an alternative to traditional networking approaches. Facilitating the user interface between the experimenter and the facility as a tailored version of the SmartCitizen dashboard had been selected. Finally, aiming at easing the work of less experienced experimenter the Tinkerspace platform will allow these users to design and run experiments relying on a very intuitive graphical framework of a similar form to LEGO in simplicity and component building. Additionally, hardware/middleware platforms such as SENSINACT, Eventbus and TSmarT, DULradio have also been considered for further integration.
We have provided a concrete set of requirements for the main functional features of the OrganiCity plat-form such as platform management, user authentication/authorization and experimentation support. With all these considerations, an initial architecture accommodating a prioritized list of requirements was postulated. Essentially, it specifies a uniform API, which exposes observations making use of the data model agreed within the consortium. This API interacts with each site’s methods and enablers through the implementation of particular required adaptors. The SmartCitizen dashboard allows the depiction of the values gathered from the different sites. Further work in terms of the management of historical data will be carried out in WP2 and eventually WP3. We translated the initial ideas of the consortium about the OrganiCity facility and requirements gathered by the user community into an overall architectural vision for the project. It served as an initial guideline for the research and development activities in the technical work packages of the project dealing with the delivery of an integrated experimentation as a service facility (WP2) and co-creation tools (WP3).
A first major challenge was the integration of heterogeneous assets from different city eco-systems, such as different open data platforms, IoT middleware and devices into a common experimentation platform. Addressing the resulting interoperability challenges requires an agreement on APIs and information models for the description of heterogeneous assets and data exchanged through these APIs. In the task we had outlined a strategy of how this can be achieved for the three participating consortium cities Aarhus, London and Santander.
The specification efforts in this task went hand in hand with the detailed design and implementation efforts in WP2 and WP3. An alignment of APIs to expose assets at the three different sites has been performed in WP2 and more detailed specification are currently being developed taking into consideration the overall guidance provided in the task. The same alignment took place in WP3 with respect to the overall tools with a major initial focus on the urban data observatory.
In order to ensure a broader reach of the proposed integration approach to other city-ecosystems in the world, OrganiCity had deliberately chosen to align the specification with the Open & Agile Smart City initia-tive, which it is spearheading with other European organizations and cities. This initiative has already gath-ered a commitment from more than 60 cities in Europe and other parts of the world. The alignment with OASC recommendations will ensure that OASC cities can easily contribute their assets to the OrganiCity facility to make sure that OrganiCity becomes a facility for innovative city making, but especially a move-ment. The OrganiCity project will ensure that experiences in Santander, London and Aarhus are shared with other cities and that learnings and recommendations from other cities can be reflected on the facility architecture. The OASC will serve as primary engagement channel with the cities community.
This work performed in the first year was a starting point for an initial architectural vision. During the sec-ond year the OrganiCity facility architecture must evolve in order to take into consideration experiences from implementation facility use by the community.

Contributions from partners to the work in 2015 and future work:
Alexandra Institute A/S (AI)
AI is the WP1 and T1.2 lead, and is involved in all tasks. In year one AI has conducted and participated in workshops, hackathons, open call events, etc. Additionally, AI has been development lead on the scenario tool, the main author of D1.4, and has developed the methodology for capturing community knowledge and translated this knowledge into technical requirements for the OrganiCity facility developments. Additionally, AI has participated in the discussions around architectural vision and guidelines for the technical OrganiCity developments.
In year two AI is focusing on community engagements through more workshops, different types of events, and supporting experimenters. Furthermore, AI will maintain and further develop the scenario tool and drive the expansion of the scenario portfolio. Finally, AI is focusing on generating technical requirements for the OrganiCity facility.

Aarhus University (AU)
AU is involved in all three tasks T1.1, T1.2 and T1.3. In year one, AU has, through its active role in the part-nership Smart Aarhus and the national Danish Smart Cities network, as well as its presence in diverse social media channels supported the high level of engagement with relevant communities. Information on OrganiCity has been disseminated at Internet Week Denmark Aarhus (http://internetweekdenmark.com) and AU has been present at workshops, roundtables and other events to spread awareness of OrganiCity. AU has contributed to the Community Engagement Landscape Survey, provided insights to the engagement principles and the journey and provided input to D1.1 and D1.4 in T1.2. AU has contributed to gathering use cases and end-user requirements and in T1.3 in translating these requirements into concrete service functions and high-level interfaces for the facility.
In year two, AU will further strengthen its community engagement, through ethnographic studies, as well as through actively contributing to workshops and events that promote and explain the OrganiCity facility. AU will also contribute to the architectural proposal for the OrganiCity facility and ensure alignment with the work being done in WP5 and WP6.

Intel Corporation (INTEL)
In year one INTEL has contributed to deliverable D1.2, participated in all co-creation workshops at the London Cluster, contributed to requirement Analysis under Technical perspectives of use-cases and interactions with the London communities in order to provide input for further analysis to T1.2, T1.3 and WP2, WP3. Additionally, INTEL has engaged the research/academia community at several workshops and conferences. Furthermore, INTEL has contributed to D1.4, and contributed to the methodology of creating and analysing OrganiCity scenarios, as well as the design and development of the scenario tool (API method implementation, database design and so on). INTEL has contributed to D1.6 (lead on the creation and editing of this deliverable), and finally, INTEL has contributed to the technological analysis of existing infrastructures of Cluster Sites and base ground technologies, and tools provided by the members of the consortium. Formal Requirement ana

Progress beyond the state of the art and expected potential impact (including the socio-economic impact and the wider societal implications of the project so far)

The core impact of the OrganiCity facility will first be fully realised when experimentation enabled through the first open call, launched in 2016, has taken place. Impact so far has been achieved through community engagement and awareness activities, especially within the context of the Open & Agile Smart Cities initiative, in which OrganiCity has been a key driver.

Related information

Record Number: 186686 / Last updated on: 2016-07-14