Guiding Questions

Purpose of this Building Block Component: The offering comprises data assets and associated services that enable use cases. This includes: data products and services.

It is essential to bundle offerings in a way that reflects user needs (e.g. emissions dashboard for real estate owners; API-based footprint verification for consultants).

This should also account for:

• Licensing models

• Terms of use

• User support services

• Interoperability with EU data infrastructure (e.g. Data4Sustainability, EUDR registries)

A well-structured offering enhances usability, legal certainty, and trust, increasing uptake and long-term engagement.

Data products: structured environmental, spatial, emissions, material flow, or asset-level data

Services: access control, consent management, data quality assurance, enrichment tools, compliance reporting modules

Purpose: Clearly structured environmental, spatial, emissions, material flow, and asset-level data.

1. Data Products

• What key data assets will be initially offered?

• How will data assets be standardised and validated?

• How frequently will data be updated and shared?

• How can data products be designed to be modular and reusable across multiple use cases?

• How can data assets be standardized and validated efficiently?

• How can offerings remain aligned with participant needs over time?

1. Functional Questions:

• What data model will be used?

1. Functional/Technical Questions:

• How can offerings remain aligned with participant needs over time?

• What is the source of the data?

Purpose:

• Data access control & consent management

• Data quality assurance & validation

• Data enrichment tools (e.g., analytics, visualisation)

• Compliance reporting modules (aligned with CSRD, etc)

1. Associated Services

• Which services are critical to the initial use cases?

• How will compliance and consent management be technically enforced?

• What are the minimum standards for data quality assurance?

• Which services add the most value to participants while remaining interoperable?

• How should services be prioritized based on current and future use cases?

Purpose: Licensing models clearly aligned with open data standards or commercial/regulated usage. Define clear terms of use, including IP rights, access rights, and permitted usage.

1. Licensing and Terms of Use

• Under which license models will data be provided?

• Are there specific data-usage restrictions or access tiers?

Purpose: Define helpdesk, training resources, and dedicated support channels.

1. User Support

• How will support needs differ across stakeholders (public/private, technical/non-technical)?

• Who will deliver these support services (in-house, third-party)?

• How can support resources be tailored to different types of participants?

• How can training ensure quality data contribution?

Purpose: Alignment with EU-wide data infrastructures (Data4Sustainability, EUDR registries, Copernicus) and Common EU Data Spaces (CEADS, EMDS, etc). Define Standardised data formats and APIs.

7. Interoperability

• Which external EU registries and frameworks should be integrated to ensure compliance and interoperability?

• How will ongoing alignment with evolving EU data interoperability standards be ensured?