Organisational/operational building blocks

Definition

The organizational level refers to the way in which the agreements, expectations and processes are aligned to achieve the common goals for controlled data sharing. This includes the onboarding and certification (according to common and accepted criteria), aligned service level agreements (for realizing overarching expectations and quality control) and aligned operations and customer processes (for improved operating efficiency and enhanced customer experience).

Role and Scope

Features

Design Principles Position Paper
  • Domain Data Standard

  • Unique Identifiers

  • Authorisation Registries

  • Trusted Parties

  • Data Space Boards

  • Overarching cooperation Agreements

  • Continuity Model

  • Regulations

Components and Technologies

i3-Market Project
  • Embedded Ledger

  • Database

  • Smart Contracts for Permissioning

  • Synchronization: The distributed storage database must support data synchronization between nodes.

  • Semantic Database

  • API for External Access

For more detailed information, visit the source's webpage.

EGI - ACE
  • ITSM Coordination, an IT Service Management (ITSM) framework based on FiTSM

iSHARE Foundation

European Union Agency for Railways - ERA
  • Ontologies KNOWLEDGE graph

  • Shacl

  • Linked data

  • FAIR principles

MyData

The ecosystem created by operators, working with data sources and data using services, is always part of a broader, social and economic system of individuals, communities, public organisations and private companies. Therefore, the ecosystem functions within the wider context of legislation, regulation, and social norms. Legislation is necessary for the creation of trust, but it is not sufficient. In order to create a level playing field in the market, rules of engagement between the different roles and actors fulfilling those roles are needed.

Read more in Understanding MyData Operators

i4Trust
  • i4Trust technology building blocks can be used with different governance frameworks but the one implemented by iSHARE is given as one possible reference.

Technical Reference Implementation

iSHARE Foundation
European Union Agency for Railways - ERA
i4Trust
  • See this for an example of governance that can be implemented for data spaces using i4Trust building blocks.

Business Use Cases Implementation

EGI - ACE

ITSM Coordination oversees the implementation and evolution of the IT service management system across EGI. The service designs and implements structured processes for the improvement of service delivery to its customers.

iSHARE Foundation

iSHARE is used in a lot of existing data spaces: Logistics, Energy, Building, Agriculture, Maritime.

Best practices identification and recommendations

EGI - ACE
  • Repeatability: Services and processes operate the same way time after time.

  • Quality: Repeatable processes can be monitored and optimized to increase quality.

  • Demonstrability: Following a standard allows quality to be audited and demonstrated to others.

  • Compatibility: Managed services can be combined with other services by customers, or in federated provision scenarios.

  • Professionalism: Formally managed services appear more professional to customers.

iSHARE Foundation
  • A generic legal framework severely lowers the threshold of sharing confidential data.

European Union Agency for Railways - ERA
  • FAIR

Gap or what is missing?

EGI - ACE
  • Network of Trainer for FiTSM.

TRL

Comments

Additional Information

EGI - ACE
iSHARE Foundation
European Union Agency for Railways - ERA

Last updated

© 2016 – 2024 | All Rights Reserved | International Data Spaces Association