BP02E - Governance Authority monetisation model configuration

To help understand the content of this document, readers should familiarize themselves with the key definitions and actors.

Overview

 

Governance Authority Monetisation Model Configuration is a subprocess of BP02 – Configuration of data space Governance Authority process. It supports the definition of a model for Governance Authority monetisation, which outlines the definition of rules, structures, and triggers that support the implementation of the Governance Authority monetisation strategy implemented through Simpl-Open configuration and supporting integration mechanisms. The monetisation model operates as a policy and configuration layer. BP02E defines the monetisation - related commercial terms and conditions applicable to Participants access to the data space.

Monetisation Model configuration lifecycle:

  • Creation: the monetisation model/configuration is created and, once activated, can be assigned to Participants following their acceptance. Until the Participant explicitly accepts it, the Participant remains blocked from accessing the functionalities subject to the monetisation model.
  • New version of an existing model: the previous version remains applicable to Participants already assigned to it until they accept the new version. New Participants cannot be assigned the previous version.
  • Direct deprecation without a replacement/new version: the model is discontinued immediately, including for Participants currently assigned to it.

Actors

The following actors are involved:

  • Governance Authority
  • Data Space Participant (Consumer or Provider)

Assumptions

The following assumption is made:

  • The Governance Authority is responsible for ensuring that all configured rules are legally compliant and consistent with the contractual terms presented to Applicants during onboarding.

Prerequisites

The following prerequisites must be fulfilled:

  • Governance Authority user authenticated and authorised: the Governance Authority user performing the configuration is authenticated in the Governance Authority agent and authorised to manage the Governance Authority monetisation model (BP02).

Details

The following shows the detailed business process diagram and gives the step descriptions.

 

Trigger data space monetisation model configuration

The data space Governance Authority decides to monetise their data space activities and initiates the data space monetisation model configuration.

BP02E.01 Assign a monetisation model

The Governance Authority identifies and assigns a single monetisation model per Participant type in the data space. The current available models are: One-off fee, periodic subscription, transaction-linked fee, or tiered access.

BP02E.02 Configure monetisation model parameters

The Governance Authority specifies the applicable conditions for the selected model. Depending on the selected model, it is necessary to define different parameters such as transaction-linked fees (fixed amount or %), periodicity (e.g. monthly and/or annual) and tier definition. Regarding tier definition, the Governance Authority must establish the different tiers that will be offered (e.g. Free or Premium) and a description of service access and capabilities per tier.

BP02E.03 Define a Dunning policy

The Governance Authority defines the Dunning policy applicable for the configured monetisation model. The Dunning policy specifies the rules and thresholds that trigger specific enforcement actions based on payment status (e.g. grace period definition, severity thresholds, enforcement actions per severity level, reinstatement conditions). Possible enforcement actions include notifications, service access restriction, tier downgrade, Participant flagging, etc.

BP02E.04 Validate model configuration

Monetisation model configuration is first validated to ensure completeness and consistency. If the configuration is incomplete or inconsistent, the outcome "Configuration incomplete or inconsistent" occurs and configuration activation is blocked.

BP02E.05 Activate model configuration

Upon successful validation, the Governance Authority activates the configuration within Simpl-Open. Once a model configuration is active, it can be associated with Participants. Activated configurations are versioned and timestamped for auditability.

BP02E.06 Inform about the activated model and ask for acceptance of terms

If there are already Participants of the type to which the model applies, they shall be informed and asked to agree the terms and conditions related to the applicable active model. If the Participant is not reacting to the request for accepting the new terms and conditions, the Governance Authority will have to act, based on the agreements and policies of the data space shared when onboarding.

BP02E.07 Participant accepts terms of a monetisation model

A data space Participant agrees to the terms of the monetisation model applied to their Participant type.

BP02E.08 Apply monetisation model for a Participant

The Governance Authority receives the Participant's acceptance of the monetisation model terms, records it, and applies the monetisation model for that Participant.

BP02E.09 Create a new version of a model configuration

The Governance Authority selects a previously active model configuration and initiates the creation of a new version of this model configuration.

BP02E.10 Update monetisation model parameters

Similar to step BP02E.02 the configured parameter specifications of a monetisation model can be updated for a new version of a model configuration.

BP02E.11 Update Dunning policy configuration

Similar to step BP02E.03 the Dunning policy of a monetisation model can be updated for a new version of a model configuration.

BP02E.12 Deprecate previous version of the model configuration

Once a new version of a model configuration is validated and activated, the Governance Authority immediately deprecates the previous version and implements the new one.

BP02E.13  Directly deprecate a model configuration without replacement

The Governance Authority decides to deprecate an active model configuration without a replacement. The model configuration is deprecated immediately and can no longer be applied to Participants. From that point, Participants associated with the deprecated model configuration remain without an active monetisation model until a new model configuration is applied to them (see BP02E.01).

BP02E.14 Inform about deprecation

If a model configuration is deprecated, the Participants of this monetisation model are informed about the deprecation.

Outcomes
  • Model configuration incomplete or inconsistent: Configuration flagged for review; activation blocked until all mandatory requirements are defined and validated.
  • Model configuration deprecated: The deprecation of an existing model configuration is an outcome of monetisation model configuration.
  • Monetisation model applied for a Participant: The monetisation model is applied to a Participant once the Governance Authority has activated the model configuration and received that Participant's acceptance of its terms.

 

High Level Requirements

  • 2E.1 - The Governance Authority assigns a new monetisation model
    Simpl-Open shall support the Governance Authority in assigning and configuring ...

    See more details

  • 2E.2 - The Governance Authority defines and maintains monetisation model parameters
    Simpl-Open shall support the Governance Authority in defining and maintaining ...

    See more details

  • 2E.3 - The Governance Authority defines and maintains Dunning policy
    Simpl-Open shall support the Governance Authority in defining and maintaining ...

    See more details

  • 2E.4 - The Governance Authority activates a monetisation model configuration
    Simpl-Open shall support the Governance Authority in activating ...

    See more details

  • 2E.5 - The Governance Authority validates a monetisation model configuration
    Simpl-Open shall support the Governance Authority in validating ...

    See more details

  • 2E.6 - The Governance Authority deprecates a monetisation model configuration
    Simpl-Open shall support the Governance Authority in deprecating ...

    See more details

  • 2E.7 - The Governance Authority informs a Participant about the activation of a monetisation model configuration and asks for acceptance of applicable terms
    Simpl-Open shall support the Governance Authority in notifying...

    See more details

  • 2E.8 - The Governance Authority applies a monetisation model to a Participant
    Simpl-Open shall support the Governance Authority in assigning and enabling ...

    See more details

  • 2E.9 - The Governance Authority creates a new version of a monetisation model configuration
    Simpl-Open shall support the Governance Authority in creating ...

    See more details

  • 2E.10 - The Governance Authority reviews monetisation model configuration history
    Simpl-Open shall support the Governance Authority in accessing ...

    See more details

 

Business ProcessStatus: Proposed

Back to Simpl Business Processes

Comments (3)

Default profile image
matthias buchhorn

Community Note: Simpl-Open shall let the Governance Authority define pricing rules that depend on attributes of the requesting participant (for example a category such as public body, academic or micro-enterprise), and that split the amount between the Governance Authority and one or more providers.

GIVEN a monetisation model with a reduction for one participant category and a split between the authority and the providers
WHEN a participant of that category requests access involving two providers
THEN the amount is computed with the reduction, divided into the authority's share and each provider's share, and the calculation is recorded for audit.

Example: fees in the European Health Data Space are cost-based, split between the access body and the data holders, and reduced for public bodies, academic researchers and micro-enterprises (Art. 62).

Background: gap analysis between Simpl-Open and the adopted European Health Data Space Regulation, https://github.com/ma3u/MinimumViableHealthDataspacev2/blob/main/docs/s…

* I'm not part of the SIMPL consortia. I’m speaking as SIMPL Community member and IDSA, Eclipse Dataspaces, EHDS Open Source contributor.

Default profile image
Fernando Baeza Benjumea

Hi Matthias,

Thank you for sharing this detailed proposal. We appreciate your contribution to the Simpl-Open's ongoing evolution.

The relevant team will review your comments, and we will follow up if any further clarification or discussion is needed.

Default profile image
matthias buchhorn

Thank you Fernando, I will attend the SIMPL hackathon on Dec 09th, 2026 to discuss this future extension. I'm happy to contribute to the SIMPL community.


Please log in or sign up to comment.