Use-cases requirements, challenges and way ahead – TEADAL’s perspective

Technologies developed in TEADAL will be validated through a number of pilot cases, covering most of the Common European Data Spaces (have a look at them in detail in TEADAL’s pilot page). The requirements of the pilot cases will help to steer the development.

TEADAL - Evidence-based medicine

Smart health

Evidence-based medicine

TEADAL - Mobility federated access point

Smart mobility

Mobility federated access point

TEADAL - Smart viticulture data sharing

Smart viticulture

Smart viticulture data sharing

TEADAL - Industry 4.0 fast KPI calculation

Industry 4.0

Industry 4.0 fast KPI calculation

TEADAL - Shared financial data governance

Smart financing

Shared financial data governance

TEADAL - Regional planning for environmental sustainability

Smart energy

Regional planning for environmental sustainability

Recently, the TEADAL consortium finished the requirements analysis of the pilot cases, obtaining a unified view of their similarities and differences. The analysis included the mapping of current processes that achieve goals similar to the pilot cases, and the desired scenarios that could and should be implementable using TEADAL tools. The latter have KPIs attached to them, allowing the TEADAL consortium to gauge the progress and the success of the tools.

The common challenges of the pilot cases include large data sizes, frequent updates to data, complex data models. There are also significant differences, e.g. in the nature of federation, privacy and confidentiality requirements (including the level of complexity in policies), or geographic distribution of data producers and consumers.

Several of the pilot cases have important regulatory considerations, e.g. GDPR or domain-specific legal requirements, which can affect the choice of usable technologies and the ways of composing them. The analysis of the pilot cases continues with the identification of their common or similar sub-processes in the form of system use-cases, and by specifying the requirements to an architecture that TEADAL tools can attach to.