D2.7 CONCEPTUAL MODEL &amp; REFERENCE ARCHITECTURE
Creators: name: Sanguino Gonzalez, Maria Angeles
name: Montero Gomez, Jorge
name: Pariente Lobo, Tomas
name: Munné, Ricard
name: La Rocca, Giuseppe
name: Luna-Valero, Sebastian
name: Biran, Ofer
name: Feder, Oshrit
name: Moatti, Yosef
name: Moutselos, Kostas
name: Moulos, Vrettos
name: Tsanakas, Panayiotis
name: Michael, Panayiotis
name: Bettiol, Alberto
name: Taborda Barata, Martim
name: del Hoyo, Rafael
name: Williams, Ebenezeer
name: Frost, Sarah
name: Ali, Adil Mohammed
name: Duzha, Armend
name: Achilleopoulos, Nikos
name: Bozhkova, Petya
name: Nasias, Konstantinos
name: Sancho, Javier
name: Yovkova, Iskra
name: Oikonomou, Konstantinos
name: Ledakis, Giannis
name: Kiourtis, Thanos
name: Zaragoza, Jose Maria
name: Roldan, Jacob
name: Martinez, Patricio
name: López Moratalla, Javier
name: Ebro, Sadra
name: Maragkos, Chris
name: Maglogiannis, Ilias
name: Mavrogiorgou, Argyro
name: Manias, George
name: Marinos Sgouros, Nikitas
name: Kyriazis, Dimosthenis
Publisher: name: Zenodo
Year: 2022
Subjects: Policy Cloud
policymaking
data driven

description: The third and final version of the PolicyCLOUD Conceptual Model &amp; Reference Architecture (originally submitted as Deliverable D2.2 in September 2020 [20] with the second version submitted as D2.6 in June 2021 [21]) is presented in this document. 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 access 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 allows the definition of forward-looking policies as well as their dynamic adaptation and refocusing to the population they are applied on. Based on the project’s offerings along the main two axes of the Concept, five main building blocks (in a layered manner) 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 also includes a Data Governance Model, Protection and Privacy Enforcement and the Ethical Framework as depicted in Figure 2. The architecture allows for integrated data acquisition and analytics. It also allows data fusion with processing and initial analytics (see 7.6.5) as well as seamless analytics (see 7.6.6) on hybrid data at rest. Integration in PolicyCLOUD follows three directions: (i) architecture integration, (ii) integration with the cloud infrastructure and (iii) integration with Use Case scenarios through the implementation of end-to- end scenarios. Additional integration activities take place along the two frameworks of PolicyCLOUD, (a) the Data Governance model, protection and privacy enforcement mechanism and (b) the Ethical and Legal Compliance framework. For end-to-end data path analysis we have used two Use Case scenarios: (i) the scenario of Use Case 1: “Radicalization incidents” and the scenario of Use Case 2: “Visualization of negative and positive opinions on social networks for different products”. <strong>The new updates in this final document</strong> provide the following: Analysis of how External Frameworks can be integrated with PolicyCLOUD (section 7.6.11.4); Presentation of the overall Conceptual View and architecture of the Data Marketplace (section 7.9.1); Outline of the mechanisms developed for initialising the Policy Development Toolkit with Policy Model components and the visualization of results (section 7.8.3); Analysis of the Ethical and Legal Compliance Framework positive interventions to the PolicyCLOUD architecture, including the addition of specific fields/parameters to the registration Application Programming Interfaces to be populated with details regarding each individual analytics tool and dataset/data source (section 7.5); Presentation of the integration of the Data Governance model, protection and privacy enforcement mechanisms with the Policy Development Toolkit, the cloud gateways and the marketplace (section 7.10.2), and within the same context, the integration of EGI-Check-in with Keycloak including the integration of the Data Governance model, protection and privacy enforcement mechanisms with the Kubernetes cluster. The document also addresses the Reviewers’ comments to the previous version of the deliverable (Deliverable D2.6), included in the second review report. In order to address these comments, additional updates of Deliverable D2.7 include: (i) links to specific user/stakeholder requirements (D2.5), (ii) descriptions and implementation details for the two remaining pilot Use Cases (Sofia and London) and (iii) reference to EOSC and to the role of the Conceptual Model &amp; Reference Architecture document for the identification of the relevant services and of their providers, and description of the onboarding process based on Deliverable D3.4 [22].
description: This deliverable is submitted to the EC, not yet approved.