Skip to main content
Building Value-Added Dataspace Services: A Guide for Consulting Companies

Building Value-Added Dataspace Services: A Guide for Consulting Companies

· 12 min read
Matthias Buchhorn-Roth
Matthias Buchhorn-Roth
Cloud & Dataspace Architect (Consultant)

In the rapidly evolving landscape of data ecosystems, consulting companies play a pivotal role. Clients are no longer just asking "how do I store my data?" but "how do I share it securely and profitably?"

For consultancies, building expertise in dataspaces is now a critical investment. The European Commission and national governments are aggressively funding the development of data ecosystems to secure digital sovereignty. This public push is reinforced by a regulatory tsunami: the Data Act, enabling users to access data generated by their devices, and the Data Governance Act, creating a framework for neutral data intermediaries. These regulations are creating a new market reality where the ability to share data in a compliant, sovereign manner is a license to operate.

As a Cloud & Dataspace Architect working in the consulting sector, I see firsthand how organizations struggle to bridge the gap between their internal data silos and the collaborative potential of dataspaces.

This guide outlines how consulting firms can build a portfolio of value-added services (VAS) that enable clients to participate in dataspaces. We will cover the end-to-end journey: from establishing identity and security to defining data products, managing contracts, and leveraging regulations as a driver for adoption.

The Consulting Opportunity in Dataspaces​

The shift to federated data sharing represents a major market opportunity for consultancies. It's not just about installing software; it's about architecting trust, governance, and business models. To capture this value, consulting firms must extend their offerings to include:

  • Management Consulting: Guiding clients through the strategic adoption of decentralized technologies.
  • Data Monetization Strategy: Designing business models to turn data assets into revenue streams.
  • Network Effect: Strategizing on how to build and grow the ecosystem to increase value for all participants.
  • Data Governance & Auditing: Establishing the rules of engagement and ensuring automated logical compliance.
  • Security & Privacy: Implementing Zero Trust architectures (referencing the NIST Implementation Guide), End-to-End (E2E) Encryption, and Confidential Compute environments.
  • Sovereign Data Storage: Ensuring data resides in compliant, sovereign infrastructure.
  • Data Transformation: Mapping and converting internal data schemas to interoperable standards.
  • Evolving Data Products: moving from static datasets to managed, evolving data products.
  • Data Mesh Architecture: Extending the Data Mesh concept to serve external customers and partners.
Strategy Tip

Consulting firms should position themselves not just as integrators, but as Eco-system Enablers. The value lies in helping clients navigate the complexity of multi-party data sharing.

Understanding the EDC Layers: The Consultant's Map​

To effectively advise clients, consultants must understand the architectural map of the Eclipse Dataspace Components. The diagram below organizes the technology into four logical layers, moving from the foundational protocols up to the ecosystem tooling.

EDC Layers

Layer 1: The Protocols (How Components Communicate)​

This is the "Step-by-Step" language of the dataspace. These are the open standards that ensure interoperability, regardless of vendor.

  • Dataspace Protocol (DSP): The core specification for publishing data offers, negotiating contracts, and initiating transfers. It is the "handshake".
  • Decentralized Claims Protocol (DCP): An overlay to the DSP for verifying identity. It uses Verifiable Credentials to establish trust before any data is shared.
  • Data Plane Signaling (DPS): The protocol that bridges the "Brain" (Control Plane) with the "Muscle" (Data Plane), allowing them to run on separate infrastructure.
  • Consulting Task: Ensure clients are not building proprietary APIs but are adhering to these standards for future-proof interoperability.

Layer 2: The Participant (Core Building Blocks)​

These are the actual software components your client needs to deploy to become a member of the dataspace.

  • Core EDC Connector: The standard software piece that combines negotiation (Control Plane) and transfer (Data Plane).
  • IdentityHub (Wallet): The digital safe. It holds the generic identity (DID) and the specific credentials (e.g., ISO certifications) that allow the connector to prove who it is.
  • Virtual Connector: A multi-tenant architecture that allows you, as a service provider, to host "Connectors-as-a-Service" for multiple clients efficiently.
  • Connector Fabric Manager (CFM): The management layer for provisioning and onboarding these connectors at scale.
  • Consulting Task: Architecture design. Deciding whether a client needs a dedicated Core Connector (high security/isolation) or can be onboarded via a managed Virtual Connector (lower cost/complexity).

Layer 3: The Network (The Glue)​

These services do not belong to one single participant but facilitate the network effect.

  • Federated Catalog: An aggregated service that crawls the decentralized network. It caches metadata so users can search across thousands of data offers instantly, rather than querying every connector individually.
  • Consulting Task: Discovery Strategy. Ensuring your client's data assets are properly indexed in the Federated Catalog so they can be found by potential buyers.

Layer 4: The Ecosystem (Demonstrators & Compliance)​

The tools used to validate, demonstrate, and test the system.

  • Just Another Demonstrator (JAD): A complete "Dataspace-as-a-Service" reference implementation. Use this to show stakeholders a working system immediately.
  • Minimum Viable Dataspace (MVD): A developer-focused sandbox for understanding the code and testing concepts locally.
  • Technology Compatibility Kit (TCK): The test suite. If your client builds a custom connector, this tool verifies it is compliant with the official standards.
  • Consulting Task: Rapid Prototyping & Quality Assurance. Use JAD/MVD to build Proof of Concepts (PoCs) quickly, and use the TCK to validate any custom development.
Key Standards Cheat Sheet
AcronymFull NamePurpose
DSPDataspace ProtocolThe core standard for negotiating contracts and transfers.
DCPDecentralized Claims ProtocolHandles identity, trust, and verified credentials.
DPSData Plane SignalingManages the technical data flow between planes.
DCATW3C Data CatalogThe standard structure for describing data offerings.
ODRLOpen Digital Rights LanguageThe language used to write usage policies (e.g., "expire after 2 days").
DIDDecentralized IdentifierA unique ID for an organization or asset, independent of a central registry.

The Industrial DSaaS Roadmap

1. Strategy & Assessment​

The common journey of the customer and the consulting company begins with valid strategy. Consultants must first assess organizational readiness and define the business case using quantitative frameworks.

  • Dataspace Readiness Assessment (BLOFT): Evaluate client maturity across five dimensions: Business (strategy), Legal (IPR), Operational (processes), Functional (requirements), and Technical (infrastructure).
  • ROI Frameworks & Business Cases: Shift the conversation from IT cost to business value. Quantify the value of data sharing through direct monetization, operational efficiency, or regulatory risk reduction.
Further Reading

2. Governance Framework Design​

A governance framework is the "Constitution" of the dataspace. Consultants play a critical role in drafting the Data Sharing Governance Authority (DSGA) structure and the Rulebook.

  • Trust Framework Architecture: Defining the Trust Anchors (e.g., X.509 CAs, DID methods) that underpin the identity model.
  • Rulebook Creation: Drafting the legal and technical policies that all participants must sign, governing liability, dispute resolution, and technical standards.
Further Reading

3. The Participant Onboarding Journey​

Aligning with the DSSC Co-creation method, consultants should guide clients through a structured lifecycle:

  1. Onboarding & KYC: Verifying the legal entity. This involves integrating existing Identity Providers (IdP) with the IdentityHub and issuance of Verifiable Credentials (VC).
  2. Assessment & Compliance: Checking internal data governance against the Rulebook.
  3. Technical Integration: Deploying the Core EDC Connector or onboarding via a Virtual Connector.
  4. Testing & Certification: Using the Technology Compatibility Kit (TCK) to validate compliance before going live.

4. Data Product Development Methodology​

In a dataspace, you don't share "files"; you manage "Data Products". This methodology covers the entire product lifecycle:

  • Definition & Semantics: Mapping internal data structures to industry standards to ensure context.
  • Discovery & Packaging: Publishing data offerings to the Federated Catalog using standard profiles like DCAT-AP or sector-specific ones like HealthDCAT-AP and MobilityDCAT-AP.
  • Policy Definition: Using ODRL to craft machine-readable usage policies (e.g., "AI training allowed", "Delete after 30 days").

5. Operations: The Runbook​

Operational Excellence is critical for stability. The runbook defines:

  • Deployment Patterns: Blueprints for deploying Connectors on cloud-native Frameworks like Kubernetes (K8s) or bare metal with Indfrastructure as Code (IaC) tools like OpenTofu and Helm, ArgoCD and Flux.
  • CI/CD & Monitoring: Pipelines for connector updates and dashboards for monitoring contract negotiations and transfer health.
  • Incident Management: SLAs and procedures for when data transfers fail or connectors go offline.
Further Reading

Dataspace Success Playbook Phase 2

6. Change Management Playbook​

Adoption is 90% human. The playbook ensures organizational alignment:

  • Stakeholder Mapping: Identifying champions and detractors.
  • Training Programs: Upskilling teams on decentralized identity, sovereignty, and new workflows.
  • Adoption Metrics: Tracking KPIs like "Active Data Contracts", "Partner Growth", and "Data Usage Volume".
Further Reading

7. Legal Deep-Dive & Future Proofing​

Beyond GDPR, the regulatory landscape is shifting aimed at unlocking data value:

  • EU Data Act: Mandating fair access to data generated by connected products.
  • eIDAS 2.0: Preparing for the EU Digital Identity Wallet as the standard for organizational identity.
  • AI Act: Ensuring transparency and provenance for data used in AI training models.
  • Data Governance Act (DGA): Regulating neutral "Data Intermediaries".
Further Reading
  • EU Data Act: The official framework for fair access to and use of data.
  • Data Governance Act: Rules for data intermediaries and altruism.
  • AI Act: The comprehensive regulation on Artificial Intelligence.

8. Provenance and Traceability Architecture​

Trust requires verification.

  • Clearing House: Deploying a neutral component that logs the metadata of every transaction (not the data itself) for audit and billing purposes.
  • Audit Logging: Ensuring immutable logs for compliance with the AI Act (tracing training data sources) and Supply Chain Due Diligence.
Further Reading

9. Cross-Dataspace Interoperability​

Silos must be broken, even between dataspaces.

  • Interoperability Design: Architecting solutions where a single participant can join multiple dataspaces (e.g., Catena-X and Manufacturing-X) simultaneously without duplicating infrastructure, using a unified Identity Hub and Connector.
Further Reading

10. ROI Frameworks & Business Case Templates​

Finally, consultants must prove value by shifting the conversation from "cost of implementation" to "cost of exclusion" and "revenue potential".

  • Value Proposition Workshops: Conduct workshops to identify high-impact use cases (e.g., CO2 reduction, inventory optimization) and map them to quantifiable financial outcomes.
  • TCO Analysis: Provide detailed models comparing the Total Cost of Ownership (CapEx of integration + OpEx of Connector hosting) against the Cost of Inaction (loss of supplier contracts, non-compliance fines).
  • New Revenue Streams: Design business models for data monetization, such as "Pay-per-API-call" or "Subscription-based data products", using the contract negotiation features of the EDC.
Further Reading

By expanding into these strategic, operational, and legal domains, consulting firms transform from specific technical implementers into essential strategic partners, guiding clients through the entire lifecycle of the new data economy.