D2.2 CONCEPTUAL MODEL & REFERENCE ARCHITECTURE

The PolicyCLOUD Conceptual Model & Reference Architecture are presented in this report (Deliverable D2.2) released in M8 of the project. Updates of the deliverable will be published in M18 and M30. The PolicyCLOUD Conceptual Model presents the overall project concept along 2 main axes. Along the first data axis PolicyCLOUD delivers Cloud Gateways and APIs to model the data sources and adapt to their interfaces so as to simplify interaction and data collection from any source. Along the second main axis the Policies Management Framework of PolicyCLOUD is exploited for the definition of forward-looking policies which are dynamically adapted and methodically focused on the population that are applied on. Five layered building blocks define its Architecture: (1) The Cloud Based Environment and Data Acquisition, (2) Data Analytics, (3) the Policies Management Framework, (4) the Policy Development Toolkit and (5) The Marketplace. The architecture includes a Data Governance Model, Protection and Privacy Enforcement and the Ethical Framework. The architecture allows for integrated acquisition and analytics, as also data fusion with processing and initial analytics combined with seamless analytics on hybrid data at rest. A number of scenarios developed for the Use Cases of PolicyCLOUD are also included in the document, in order to serve as end-to-end examples for the demonstration of the data ingest flow and data exploitation and for the analysis of the processing and data transformations along the complete data path. Problem statement, main objectives, Key Performance Indicators and data sources sections are provided for each scenario in this first release of Deliverable 2.2 while the detailed end-to-end data path analysis will be prepared during the completion of the first prototypes in M10 and will be included in the next update of the document in M18. The overall architecture and Use Case scenarios have been discussed by all partners (i) during the kick-off meeting, (ii) during the development of the preliminary specification as an internal report made available to partners and (iii) during specialized internal workshops integrating constituent architectures and specialized internal workshops discussing Architecture integration and end-to-end Use Case journey. Finally, conclusions are provided in the last section of the document