Proposed activities under this call should build to the extent possible on solutions and ecosystems already existing and available at EU level.

Preparatory work shall include at least three of the following elements:

1. Mapping of the families of datasets in the field of security including photos, videos, voices samples, unstructured text (e.g. forums), unstructured hybrid data (e.g. web scraping or emails), structured data (e.g. telecommunication signalisation data), etc. The mapping should include references to existing ontologies, international standards and data models when relevant.
2. Analysis of technologies that would allow the sharing of operational data, including but not limited to data anonymisation and generation of synthetic data sets, as a possible solution in cases of legal restrictions on collection and sharing of law enforcement datasets (e.g. need for additional consent to allow new processing of data for the purposes of innovation).
3. Analysis and definition of requirements for tools for classification and annotation of data sets, including mapping of existing solutions.
4. Analysis and definition of requirements for tools for data quality assessment Analysis (including mapping of existing solutions) and definition of requirements for data management tools.
5. Analysis and definition of requirements for a code repository for these tools, taking into account existing solutions and initiatives at EU level (e.g. Europol’s developed European Code Repository, or the European Anti Cybercrime Development Association’s work on tools for annotation of data).
6. Analysis of the estimate cost of developing/acquisition of the abovementioned solutions, while taking into consideration existing initiatives in order to avoid duplications.
7. Definition of requirements for User Access Management for the national components of the Data Space
8. Defining a list of Requirements for the national components including the following (not exhaustive): private/hybrid cloud requirements; software, hardware and technologies to be used.
9. Definition of the micro/macro-services within the cloud/platform and including those in a SaaS, IaaS and PaaS ecosystem.

Technical workshops with the occasion of the submission of the mid-term progress report and the final project report. As a result of the workshops, the consortium will produce a report covering the objectives described in the previous section that had been addressed by the consortium.
The report shall include, at least, the following elements:

• A list of functional and non-functional requirements for the data sets and for the data-related national components of the European Security data space (including quality, scale, and models).
• A low-level architecture of the data-related national components of the European Security Data Space. This includes description of the solution, application and infrastructure (hardware and software) architecture.
• Limited list and content/model of datasets

In case the consortium delivers data sets, the deliverable would be a document providing a description of the data set (including purpose, size, origin, quality characteristics and conditions for access). The consortium should make sure that the created data set(s) is/are accessible to the relevant Member State authorities and EU Agencies at no cost. In case the consortium opts to deliver data models for specific use cases, instead of the data sets themselves, these should be defined accordingly.