ClouT ended June 2016, follow the project continuation BigClouT at http://bigclout.eu

Close Icon
   
Contact Info    

Deliverables Access   arrow

The ClouT project has started in April 2013. The deliverables performed so far are available and listed below.

Please complete your details with the form given in the right side of this page to get the deliverables ‘ PDF.

D1.1 Use cases and user requirements

Abstract: D1.1 introduces an initial analysis of high-level requirements gathered from the four cities participating to the ClouT project, namely, Santander – Spain, Genova – Italy, Mitaka and Fujisawa – Japan. The requirements are derived from the selected use cases, identified as sampling applications of three typical domains in the Smart City communities: Participatory Sensing (i.e. Participatory Citizens, Sensing Loop Citizens), Urban Context-aware (i.e. Multimodal Transport Services, Event Perception Support, Interactive City Infrastructure, Sharing User IoT devices in the Cloud, Augmented Mobility Point) and, Safety, Emergency and Health Management (i.e. Risk Warning & Management, Caring Elderly People, Healthy & Active walking support). These requirements emphasize how the cloud model and technologies may improve the usability and effectiveness of the Smart Cities applications overcoming most of the current challenges and limitations.

D1.2 First version of Reference Architecture and Reusable Components

Abstract: This deliverable includes a first version of the ClouT Reference Architecture for the CIaaS (City Infrastructure as a Service) and CPaaS (City Platform as a Service) layers, along with the initial proposals for reusable components. In defining the Architecture, the user-centric approach was followed; therefore this deliverable also includes the system requirements which were derived from the user/service requirements presented in the previous Deliverable 1.1 (“Use Cases and User Requirements”). These system requirements are here presented in combination with the functional models for each layer (CIaaS and CPaaS). The Reference Architecture is modelled in compliance with existing Reference Architectures (related to Cloud and IoT paradigms), extending them where needed and possible.

D1.3 Final Requirements and Reference Architecture

Abstract: This deliverable provides the final version of the ClouT Reference Architecture for the CIaaS (City Infrastructure as a Service) and CPaaS (City Platform as a Service) layers, along with final proposals for reusable components. The document is a complete report about the creation of the ClouT Architecture, starting from the description of use cases and user/service requirements (based on those defined in the Deliverable 1.1 – Use Cases and User Requirements – and reviewed according to stakeholders’ meetings and customer’s survey) and the finalization of the initial work included in the D1.2 – First version of Reference Architecture and Reusable Components (revised and improved following first project technical review recommendations). The Reference Architecture is described following a top-down approach, explain the overall architecture first and then the individual functional blocks, with all details about their integration between each other.

D2.1 Reusable components, techniques and standards for the CIaaS

Abstract: This document contains a collection of reusable objects (hardware and software components, techniques, protocols and standards) candidate to be part of the City Infrastructure as a Service layer in the ClouT Reference Architecture. All these objects – described in detail within the document – derive from the experience of each project’s partner, from pilot cities existing assets and from the state of the art.

D2.2 CIaaS specification and reference implementation – first release

Abstract: This document includes the first version of the CIaaS specification: the functional blocks listed in D1.2 – “First version of Reference Architecture and Reusable Components” – are analyzed more in the details and their main interfaces are identified. For each main functional block, an implementation section has been written, to report the actual technical details of the interactions among the various block, with the existing technologies proposed by partners.

D2.3 CIaaS specification and reference implementation – second release

Abstract: This deliverable includes the second version of the CIaaS specification: the functional blocks listed in D1.3 – “Final requirements and Reference Architecture” – are analyzed more in the details and their main interfaces are identified. For each main functional block, we focused on the implementations that have been deployed, to report the actual technical details of the interactions among the various block, with the existing technologies proposed by partners, and some considerations about security when it applies. In this second version of the specification we mainly addressed the evolution of the proposed components and the necessary wirings to make them properly interoperate.

D2.4 CIaaS specification and reference implementation – final release and feedback after field trials

Abstract: This deliverable includes the final version of the CIaaS specification: it highlights the updates, with regards to the specification included in [D2.3], of the functional blocks that implement the CIaaS reference architecture, the details and guidelines for the integration among different components, implementation results and feedbacks from the implementations and field trials, in forms of KPIs, with actual figures when available or testing methodologies when the final data are not ready at the moment of writing this document.

D3.1 Reusable components and techniques for CPaaS

Abstract: This document aims at collecting some existing and reusable components, techniques and standards, focusing on the City Platform as a Service (CPaaS) layer. They belong to various categories, such as the cloud storages, databases and standards used to access and manage data stored in the Cloud. The content of this deliverable will be used to define the Reference Architecture for ClouT – and the subsequent implementation of the Smart City Ecosystem. Therefore, not all presented objects will be used in the final version of the architecture, but only those ones that better respond to requirements.

D3.2 CPaaS specification and reference implementation – first release

Abstract: This document describes the first release of the City Platform as a Service layer of the ClouT system. The layer is composed of several components that fulfil different requirements identified in the project. Specifications of the components, as well as their first implementations are described in the deliverable. The instances of this first release are to be reused by the applications that will be developed and deployed via the first year field trials of the project.

D3.3 CPaaS specification and reference implementation – second release

Abstract: This deliverable describes the second release of the City Platform as a Service (CPaaS) layer of the ClouT system. The specified functional blocks composing this layer as well as the requirements they fulfilled have been both initially identified in the deliverable D1.3 – “Final requirements and Reference Architecture”. For each of these blocks we describe the main functionalities API of its subcomponents, the way they interact with other components, the implementations that have been deployed, and some considerations about security when it applies. The instances of this second release are to be reused by the applications that are developed and deployed via the second year field trials of the project.

D3.4 CPaaS specification and reference implementation – final release and feedback after field trials

Abstract: This deliverable describes the third release of the City Platform as a Service (CPaaS) layer of the ClouT system. For each functional block composing this layer the applied updates to fulfil the requirements, identified in the “Final requirements and Reference Architecture” deliverable [D1.3] are specified, as well as the details of the interactions among them or with the other layers. This document also includes considerations about the tests that have been implemented to validate the specification and implementation choices: what has been tested, why it has been, the obtained results and the tracks of improvements.

D4.1 Preliminary report of city application developments and field trials

Abstract: This document presents a preliminary report of the city applications and field trials development in each of the city within the consortium, and associated to the three application domains defined in WP4: urban context-aware, participatory sensing and safety and emergency management. As technical basis for undertaking these field trials, as well as for converging towards an homogeneous project architecture, different integration demos have been also carried out during this first year of the project, thus showing the interaction among reusable assets developed by different partners of the consortium.
Apart from architectural and technical issues, they have been also addressed the relation with the different stakeholders and the KPIs for assessing and validating the correct realization of the different field trials.
Finally, for each application and demo, they will be indicated the performance status by this first year, as well as the next steps to be achieved by the second year within D4.2.

D4.2 Middle report of city application developments and in-lab evaluation and field trials

Abstract: This deliverable presents a middle report of the city applications and field trials development and in-lab evaluation of them in each of the city within the consortium, thus updating the progress accomplished in the second year. Additionally to the field trials, the deliverable also includes demonstrable integration work achieved in the project’s second year integrating new functionalities from the reference architecture. Being in continuous relation with different stakeholders, KPIs for assessment and validation of the field trials have also been addressed. Finally, the performance status of application and status by this second year is reported, in addition to the next steps to be taken by the third year.

D4.3 Final report of City Application software, field trials and evaluation results

Abstract: This deliverable presents the final report of the city applications and field trials development and evaluation of them within the urban scenarios provided by the four cities in the consortium, thus updating the progress accomplished in the third year. Additionally to field trials’ update, the deliverable also relates to the development of intercontinental field trial, which gathers information from the different applications developed in the two first years of the project, relying on the communication among the different modules and entities developed within the scope of WP2 and WP3. Finally, it has been carried out the evaluation of the different field trials developed during this third year, identifying and measuring (when available depending on the scope and maturity of the field trial) the more specific KPIs as well as highlighting the different involved stakeholders.

Home Page