FOR SHARE - JULY SNAPSHOT - 20230622 Draft Use Case Accelerator - snippet

Draft building block snippet: Use Case Accelerator

Overview

The purpose of this document is to define the scope of the Use Case Accelerator building block. The objective of this building block is to support the increase of value of the data space by stimulating its use, more specifically by stimulating the development of (data-driven) applications that use the data available through the data space. We refer to such applications as ‘use cases’. At first, a use case may consist of just an idea to use certain data. Over time, the use case will have to mature, i.e., by exploration and discussion the details of the use case will become more clear. If the relevant stakeholders are convinced of the (high-level) value of the use case, it may turn into a real application. This will require business decisions.

The use case accelerator thus guides use case stakeholders in the exploration, development and onboarding of use cases. This can be done in the form of resources, e.g., tools and templates, but also by means of brokering implementation partners or use cases (UC) with similar experiences. This facilitation is optional; UCs are not obliged but recommended to use the Use Case Accelerator.

During the exploration and detailing of the use case, it is possible that a use case is abandoned or hibernated. As one cannot predict in advance what uncertainties and unclarities play a role, this is a realistic outcome of the process and should not be considered as failure.

Furthermore, an important aspect of the Use Case Accelerator is to identify potential for synergy. In other use cases participants are active and different data products are in use. New use cases can benefit from these established resources, and it is the function of the Accelerator to broker these (mutual reference), also with an eye on future interoperability.

We assume that there is a ‘Use Case Owner’ that acts as a spokesperson for a consortium that is considering to develop a use case.

 

Key elements

In order to increase the development of applications, the following elements are foreseen.

1. Use Case Definition: describes the use case in several dimensions. The level of detail will increase over time, and content may change. The definition includes the purpose of the application, identified data sources, specification of data models² and participants.

2. Use Case Registry: administration of the use cases related to a specific data space. The use cases can have one of the following states: in exploration, active, abandoned.

Relevant roles are Use Case Owner, Use Case Participant and Facilitator.

Key functions

In principle, the following basic functionalities needs to be provided. They will be further developed during the functional specifications phase.

• Introduction and Exploration: one of the key functionalities of the Use Case Accelerator is to support the use case in creating value by sharing data and understanding the value of the data space. For this it needs several sub-functions:

  • Checking principles: data-spaces adhere to certain principles such as data sovereignty and decentralisation. What are the principles of the use case and the consortium?

  • Core aspects: What are the core aspects of the use case? What is its value proposition, who is involved, what data sources are envisaged etc. (See for example Data Ecosystem Canvas).

    • Validation: the UCA should support the use case in assessing whether it meets the known success criteria for use cases.

 

• Resources: In order to support the process of exploration and definition of a use case, the UCA should provide resources to the use case, for example;

  • Examples of Use Cases (see also registry below), to inspire and learn from what is already done.

  • Templates and tools: structured approaches that can help further explore and define the use case.

  • Archetypes: patterns of use cases and data driven applications that summarize the essentials of different successful use cases.

  • Timeline: a use case does not materialize in one day, so a timeline, process model or journey in phases could guide the use case in prioritizing focus and activities.

  • Business model navigator: this is a useful tool to define how the business revenue can be derived from the use case.

 

• Services: Relevant services to come to a use case are e.g.:

  • Facilitation,

  • Implementation,

  • Business case,

  • Decision support,

 

• Brokering: use cases are interested in a certain Data Space because they see a potential for synergy in the theme of the data space, and its data sources and participants. The UCA should support the use case in identifying potential synergies such as:

  • Data products in use: which data sources of the data space would be useful for the use case?

  • Participants: which participants of the DS would be interested in the use case?

  • Interoperability: with which other use cases should the use case eventually become interoperable?

 

• Use case registration: In order to advance the creation of value (by usage of data), and adjust the strategy of the data space, it is important that the UCA is able to monitor the set and progress of use cases. Therefore, it uses and manages a simple administration e.g.:

  • Use case registry: which use cases are in view of the data space?

  • Backlog: which ideas have appeared on the radar of the UCA and could use follow up?

  • Good and successful cases: Which use case can serve as an attractor and good practice for the data space?

  • Failed and abandoned cases: Which use cases were tried and abandoned, and for what reason – this, to avoid duplication of failures.

• Use Case Simulator: As part of decision making and understanding the use case, it could be beneficial to simulate how a use case could evolve and create value. This can help to gain insights in the value of a use case. An example can be found in³

• Accounting mechanism, Payment clearing,

Dependences and relationships

Dependences and relationships (boundaries to be clarified) with other building bocks play an important role. This is an initial list and will be revised and extended later on based on the alignment with other building blocks:

• Data products: The Use Case Accelerator should support identification of data sources and potential data products.

• Governance authority (GA): The governance authority should ensure that a Use Case Owner is supported in finding similar or complementary use cases and data products. The GA may or may not execute that brokering by itself. The GA should also ensure that use cases and the relevant participants are registered.

• Roles & responsibilities: Some participants in the use case will also fulfill roles in the data space, e.g., data user or data provider. It should be clear what their rights and duties and options are.

• Intermediaries: Intermediaries can help use cases to find data sources and products and find synergies with other use cases. The GA should be aware of the intermediary.

• Operations: As operations on the data space, e.g., upgrading standards and protocols, will affect the users of the data space, it is of importance that operations can communicate with use cases, directly or indirectly, e.g., about maintenance planning.

• Business: The Use Case Accelerator stops where business (of the application) begins. The use case accelerator helps to identify the necessary inputs for specification of the business model.

• Governance framework: Use cases are subject to the governance of the data space.

• Legal building blocks: Use cases are subject to regulations and are responsible for being compliant. Furthermore, the governance of the data space may put additional requirements on a use case. However, the data space may also provide services that make it more easy for the use case to be compliant.

 

Relevance for the data space

The Use Case Accelerator is a key, but optional, building block for the data space. Without this building block the data space is expected to have more challenges to support the actual usage of the data space, as the value of a data space is largely determined by its use.

 

 

¹

² Semantic Layer/Digital Twins | Catena-X

³ Stolwijk, Claire, and F. T. H. M. Berkers. Scalability and agility of the smart connected supplier network approach. No. TNO 2020 R11179. TNO, 2020.

^I