9B – Consumer receives data processing service over a dataset via an application

9B – Consumer receives data processing service over a dataset via an application

Description

To help understand the content of this document, readers should familiarize themselves with the key definitions and actors and the business process introduction containing the diagram legend.

This business process outlines the indirect consumption of a data resource by a consumer through an application provided by a data provider. Data providers enable consumers to access an application that offers restricted viewing (such as read only) or processing capabilities over the data resource.

Scenarios:

Scenario 1: A stand-alone application will be deployed on a dedicated infrastructure resource per Consumer
In this scenario, the data provider provisions dedicated infrastructure for each consumer, deploying an application that has access to, and processing capabilities over the data source. The consumer only receives access to the application endpoints (e.g., web interface), allowing them to perform various processes on the data source, such as data analysis.

Scenario 2: Shared Access to an Existing Application

In this scenario, deploying a dedicated application for each consumer is not feasible (e.g., due to expensive licensing). Instead, consumers gain access to an existing application. The type of access depends on the application and the provider, and is not controlled by SIMPL, beyond what's indicated in the contract. For instance, the application may have its own identity and access management system, allowing the creation of new user accounts for consumers or providing temporary access.

The following actors are involved in the process: Data Provider, and Consumer.

Prerequisites:

The prerequisites for this business process are outlined below. These prerequisites must be met to enable the process to occur:

• Consumer / Provider Onboarded: Both the Consumer and Provider must complete the onboarding process (Business Process – 3A) before they can consume or provide any available resources;
• End User Authenticated & Authorised: The End User is authenticated and has the appropriate role and permissions to perform the steps in the process (Business Process – 3B);
• Resources registered at data space connector: The data space connector is the component to control and ensure data exchange. Hence the resource must be registered as asset first to define the contract negotiation id needed for the resource descriptions to start contract negotiation.
• Resource description is present in the catalogue: A Resource Description must be published in the catalogue for the Consumer to locate a resource in the dataspace (Business Process – 05). It is assumed that the Consumer has searched the catalogue and found the Resource Description (Business Process – 06).

Business Process Diagram & Steps:

This chapter presents a diagram visualising the business process, labelled with specific steps. Each step is further detailed in the accompanying 'Step Description'.

Step Description:

Below is a description of the steps involved in this business process. Each step outlines the specific actions and decisions required to successfully complete the process:

1. Request Service: The Consumer initiates the process by requesting a specific data service (e.g., visualisation or analytics) over a dataset from the Data Provider. This request is based on the information found in the catalogue, which was previously searched and identified by the Consumer.
2. Verify existence of agreed Usage Contract: The Data Provider verifies whether the Consumer has a Usage Contract to ensure the Consumer already has or needs to sign the relevant Usage Contract. If there is already an existing contract in place then the process continues to step 06 or step 08 for scenario 1 and scenario 2, respectively. If there is no contract the process continues to step 03.
3. Enforce access policy: The Data Provider verifies the Consumer description details (as described in their Self-Description), to ensure that according to the access policies, they are allowed to access the requested service. 
4. Terminate process: If the Consumer does not have the required permissions and conditions, or fails the access policy check, the process is terminated, and the Consumer is notified.
5. BP - 07B - Consumer establishes a Usage Contract with the Provider for selected Catalogue items: A contract is being established to articulate and govern the obligations of both the Data Provider and the Consumer, ensuring mutual compliance and clarity in the terms of engagement. This contract outlines the obligations of both parties, including the duration of access, permitted uses of the data services, and any associated fees for the Consumer, as well as the Provider’s responsibilities in delivering the agreed-upon services. The entire process can be seen in business process - 07.
6. Provisioning of the infrastructure instance: If based on the selected offer and the contract, scenario 1 is in place, a dedicated infrastructure instance is going to be provisioned within the the boundary of the data space, and as described in business process 08, to host the application (in step 7) for the Consumer. The provisioning happens automatically via the infrastructure provisioning mechanism, and the deployment script that is linked to that specific service offering / contract. 
7. Deployment of the application: A dedicated application will be deployed over the infrastructure resource which was provisioned in step 8. The deployment can happen automatically via the infrastructure provisioning mechanism, and the deployment script that is linked to that specific service offering / contract. 
8. Create Access: The Data Provider grants the Consumer access to the application. In Scenario1, it can be automatically done in the post configuration processes, depending on the type and capabilities of the application. In scenario 2, it's outside the scope of SIMPL, and may be done manually or automatically. Also if Scenario 2 is offered, the provisioning or use of an infrastructure outside the boundary of the data space is probable, which will not be controlled by SIMPL. 
9. Establish access channels for service consumption: The Consumer receives the the details of the proper access channels and the access details. 
10. Access the service: The Data Consumer accesses the service/application.

Associated L1s - High Level Requirements

• To be determined

   

Back to Simpl requirements overview