Europe is on its way to generate and make use of more data than ever. The project PrepDSpace4Mobility aims at contributing to the development of the common European mobility data space by supporting the creation of a technical infrastructure that will facilitate easy, cross-border access to key data for both passengers and freight. Given the enormous potential of data and digital technologies, the project is expected to have a positive impact on European competitiveness, society, and the environment. We invited experts in the field of mobility, transport and data space technology to join PrepDSpace4Mobility expert workshop #1 to learn more about the preliminary results of the project and give early feedback in order to sharpen the focus as needed and requested from the real market. Project PrepDSpace4Mobility is Funded by the European Union and coordinated by acatech (Germany), activities are carried out by Amadeus SAS (France), EIT Urban Mobility, an initiative of the European Institute of Innovation and Technology, a body of the European Union, (Spain), FIWARE (Germany), FhG (Germany), IDSA (Germany), iSHARE (Netherlands), TNO (Netherlands), USI (Germany), VTT (Finland), EMTA (France), Group ADP (France), KU Leuven (Belgium), ERTICO (Belgium), BAST (Germany), UIH (Hungary), and MDS (Germany).

1. Funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Commission. Neither the
European Union nor the granting authority can be held responsible for them.
Work Package 3, Task 3.4 (Building Blocks)
Methodological approach and Roadmap

2. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Task 3.4 Objectives
• Subtask 3.4.1
• Identify governance frameworks, reference architectures, etc. eligible for analysis​
• Analyze the governance frameworks, business models and other strategies for
proposed BBs​
• Analyze the identified data sharing ecosystems for inherent, sector specific BBs
• Subtask 3.4.2
• Work on the proposal of common mobility-specific building blocks and requirements
using the specifications elaborated by Task 3.4.1​
• Suggest incentive schemes to motivate participants to provide data​
• Identify legal avenues to foster data reuse in mobility, such as the revision of legacy
legal frameworks​
• Contribute to a graphical representation of the project’s findings​

3. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Methodology for Analysis of Building Blocks
TOP-DOWN MEETS BOTTOM-UP: REFERENCE ARCHITECTURES MEET BEST PRACTISE
Define the Data Space Capabilities
analysing Theoretical Architecture and
Building Blocks Models
BOTTOM-UP-FIRST-APPROACH:
• ANALYZE EXISTING (THEORETICAL) MODELS
• EXTRACT PROPOSED BUILDING BLOCKS
• TRANSLATE/MAP ALTERNATIVE CONCEPTS
• CONSOLIDATE CONTENT
• PROVIDES COMMON DS FEATURES
• ALLOWS FOR COMPREHENSIVE PICTURE
• ENRICH LATER WITH BEST PRACTICES
REPRESENTATIVE GUIDELINE FOR THE
IMPLEMENTATION OF DATA SPACES
BOTH A TOP-DOWN AND BOTTOM-UP APPROACH HAVE THEIR LIMITATIONS
RISKS AND OBSTACLES:
• SEVERAL DIFFERENT MODELS NEED TO BE ANALYZED
• MAPPING MIGHT BE DIFFICULT
• CONSOLIDATION INTO ONE FINAL MODEL WILL BE TIME CONSUMING
• PROBABLY POOR INPUT REGARDING BUSINESS MODELS AND INCENTIVES
• WORK SUPPOSED TO BE DONE BY DSSC
Identify Building Block Requirements by
investigating existing Best Practises from
representative Use Cases

4. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
TOP-DOWN MEETS BOTTOM-UP: REFERENCE ARCHITECTURES MEET BEST PRACTISE
Identify Building Block Requirements by
investigating existing Best Practises from
representative Use Cases
Define the Data Space Capabilities
analysing Theoretical Architecture and
Building Blocks Models
TOP-DOWN-FIRST-APPROACH:
• Analyze Existing Data Space initiatives
• Assess Each Architecture Model/Building Block “Usage”
• Business Models and incentives from Reality
• Weaknesses and strengths Experience
• Consolidate findings
• Enrich later from standard models
• Allows for pragmatic picture of the feasible
• Sector and Use Case specific features
• Needs anyway an idea of possible Building blocks
REPRESENTATIVE GUIDELINE FOR THE
IMPLEMENTATION OF DATA SPACES
BOTH A TOP-DOWN AND BOTTOM-UP APPROACH HAVE THEIR LIMITATIONS
RISKS AND OBSTACLES:
• Small number of sufficiently advanced projects
• Poor responses to the surveys
• Not all BBs considered
• Great variety of information formats

5. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Methodology for Analysis of Building Blocks - A Best Practices Approach:
1. Survey within all members of the inventory on:
• Data sharing architecture, Building Block usage, Governance Processes, Business Models, based on
the OpenDEI BB Schema, plus attractors, showstoppers
2. Generation of a refined view on data space design with selected DS:
• Survey on the implementation of capabilities in detail (enriched OpenDEI capabilities catalogue)
• Reasons for absence of capabilities
• Adherence to legal constraints
3. Validate with representative Use Cases
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
“TOP DOWN” APPROACH
Your
Input is
highly
desired!!

6. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
• Questionnaire I addressing the needs for both T3.3 and T3.4
• Addressing the required inputs for both T3.3 and T3.4:
• Addressing cornerstones of data usage
• Asking for technical and organisational Building Blocks
• As refinement for each of the (extensive set of) contributions / entries in the WP2 Inventory
1. What type of data sharing is supported?:
a. Sharing of persistent (semi-static) data
b. Sharing of (real-time) streaming data
c. Algorithm sharing for local processing of (sensitive) data
d. Smart contracting for data flow control
e. Multiple of the above
f. None of the above
Additional Remarks (open question)
1. Do you (plan to) adopt a building block implementation according to
an EU Reference Architecture Initiatives
a. Building blocks from the IDSA Reference Architecture?
b. Building blocks from the GAIA-X Reference Architecture?
c. Building blocks from the ISHARE Reference Architecture?
d. Building blocks from the SIMPL Reference Architecture?
e. Building blocks from the FEDeRATED Reference Architecture?
f. Building blocks from another Reference Architecture?
g. Mix of elements from different Reference Models
Additional Open Questions:
∙ What building blocks of these EU Reference Architectures do you use or
plan to use?
∙ What is the motivation for using the building blocks from the selected EU
Reference Architecture(s)?
• Example (in development)
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
DATA NEEDS (TOP-DOWN)

7. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
• Interviewing selected stakeholders for technical and organisational best practises
• Based on a more detailed questionnaire II
Metadata and Discovery Protocol Are all actors/elements in the DSP described?
Which description formats are used?
Were domain-specific descriptions (elements) applicable?
Which technologies are implemented for the handling of the description?
Which parts of the implementation reside in the connector/on party-side, which in a federated soft infrastructure?
Data Usage Accounting Are the events triggered by actors logged, counted, compiled for the use in clearing, payment, and billing procedures?
Which parts of the implementation resides in the connector/on party-side, which in a federated soft infrastructure?
Publication and Marketplace Services How is the body of data descriptions made public?
Which catalogue technology is used?
How is the catalogue linked to other functions of the soft infrastructure (smart contracting, monitoring/accounting)?
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
DATA NEEDS (TOP-DOWN)

8. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Sharing of
(semi-static)
data
Sharing of
(real-time)
streaming data
Algorithm sharing
for local
processing of
(sensitive) data
Smart contracting
for data flow
control:
Personal Mobility
CCAM
Logistics Route and Load
Planning
Talking Traffic FEDeRATED Event
Driven Link Distr.
Talking Trucks
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
TOP-DOWN MEETS BOTTOM-UP: USE CASES TO VALIDATE PROPOSED BUILDING BLOCKS
Logistics Use Case
Taken from DASLOGIS
project
Tbd: REPRESENTATIVE AND ILLUSTRATIVE USE CASES
PER TOPIC MDS TOPIC AREA

9. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
OUTCOME OF THE ANALYSIS
Discover key insights that will result from this analysis and in-depth expert interviews to help support the framework
towards a European Mobility Data Space:
Outcome #1 – quantitative
• List of commonly considered Building Blocks/Capabilities
• List of sector specific Building Blocks
• List of example Use Cases of the sector (already implemented, or under work)
Outcome #2 – qualitative
• Understanding of common interpretation of necessary data space characteristics (technical and organizational)
• Identified enablers for data sharing; e.g. attractive business models, innovation opportunities, efficiency
• Common access barriers preventing potential players to enter data space ecosystems

10. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Feb Mar Apr May Jun Jul Aug Sep
Building Block
Identification
First survey /
Capability
Cataloque
Survey Analysis / Interviews / Consolidation / Validation/
Documentation
Review/Fine
tuning/Presentation
Compliance /
Legal
Scope
definition
Detailed description of resulting capabilities and non-functional
requirements, incl. impact on other capabilities
Review/Fine
tuning/Presentation
Deliverable
preparation
Deliverable preparation
Methdology
G&O analysis
data sources
Collection / Survey Analysis / Interpretation of findings /
Consolidation / Documentation
Review/Fine
tuning/Presentation
Inventory
/ Initial
survey
TIMELINES LOCKS
FOR BOTH TASK 3.3 AND TASK 3.4

11. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
METHODOLOGY FOR ANALYSIS OF BUILDING BLOCKS
NEXT STEPS FOR THE BUILDING BLOCK ANALYSIS
•February:
•Finalize the first questionnaire (Feb 10th )​
•Distribution of Questionnaire I (H2 Feb)
•Extend the capabilities draft catalogue (End of FEB)
•Elaborate applicable legal constraints (End of FEB)​
•March:
•Initialize the Deliverable Document
•Analyze the responses to Questionnaire I
•Identify stakeholders for detailed investigations

12. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
1. On the methodology presented
1. About the Collaboration with PrepDS4Mobility
1. Involvement / role of the WP3 partners:
• For both T3.3 and T3.4
QUESTIONS AND DISCUSSIONS

13. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.

14. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Backup Slides

15. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Task 3.4 Data Needs (Top-Down)
• Information needs from Inventory entries
• List of „True“ data space ecosystems
(mandatory)
• Architecture
• Building Block usage
• Governance Models
• Business Models
• TOMs to achieve compliance with regulations
• „Showstopper“
• Attractors

16. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Open DEI Technical building blocks (preliminary list)
BUSINESS APPLICATION SOFTWARE Out of scope
Data Services (OTHER) FEDERATION EXTENSION (Beyond OpenDEI)
INTER OPERABILITY
Data Analytics
Engine
Data
Visualisation
Workflow
Management Engine
Federated
Algorithms
Self Sovereignty & Reversibility
DATA VALUE
Self Sovereignty & Reversibility
Publication & Marketplace Services
Data Usage
Accounting
Data Exchange API’s Data Models & Formats Provenance & Traceability
Infrastructure
Software
Services
TRUST
Meta data & Discovery Protocol
Identity
Management
Trusted
Exchange
Access & Usage
Control/Policie
s
Systems infrastructure
(OTHER) Cloud Infrastructure Edge/On-Premises Infrastructure
Software
infrastructure
(OTHER)
System
Adaptation
Data plane
Data Routing &
Preprocessing
Data
Processing

17. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Task 3.4 Methodology (Output)
• Prepare a template for an Implementation
Backlog
• The entire project as an Epic with several
capabilities/features
• Compliance as non-functional requirements
(“Enablers”)
• Can merge input from best practise and “theory”
• Gives practical advice (best practise
recommendations)
• Does not anticipate DSSCs work

18. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Story
Story
Story
Story
Story
Task 3.4 Methodology (Output)
EPIC
Enabler
~ Building Block
~ Capability to …
~ Non-Functional Requirement
Implement a Data Space for …
Feature
Feature
Feature
Feature
Feature
Story
Story
Story
Story
Story

19. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Task 3.4 Roadmap
Feb Mar Apr May Jun Jul Aug Sep
Sector Specific
– Top Down
Initial
survey
Survey Analysis / Interviews / Consolidation / Documentation
Review/Fine
tuning/Presentation
Transversal /
Governance
Scope
definition
Detailed description of resulting capabilities and non-functional
requirements, incl. impact on other capabilities
Review/Fine
tuning/Presentation
Deliverable
preparation
Deliverable preparation

20. This project has received funding from the Digital Europe Programme under grant agreement n°101083655.
Discussion Welcome!