1 of 43

Topic 3: Operator visualisations

Diagrams [whole paper]

What diagrams / images we want to use and what do we want to communicate with them (diagrams are very powerful tools and need to be used thoughtfully)?

Memo document here

2 of 43

    • identify the parts of the paper that will be affected mostly

    • make your best realistic guess on the potentially differing views and arguments we might have in the group related to your topic, list the views

    • elaborate your base proposal on how the topic should be treated in the paper (what do we say about it and in which part of the paper and what we leave out / for future work)

3 of 43

Line of reasoning

  1. Operator thematic group wants to create a baseline paper to define the field and clarify points of discussion
  2. Different visualisations have been used to support the research
  3. We aim at the simplest, yet satisfying visualisation, to bring the message
    1. Truthful - no oversimplification
    2. Undisputed - easy to point out elements of discussion, but not taking a specific standpoint
    3. Descriptive, not normative - oriented towards functionality
    4. Aiming at pragmatics, conveying a message, not on formal semantics
    5. Should allow to pinpoint differences as well as similarities of different proto-operators, separate apples and oranges - could lead to new visualisations
    6. Hints at the complexity, exposes potential conflicts and tensions, without going “into the horrible details”
  4. Necessary: keep the MyData style in tact

4 of 43

Current images in the paper

5 of 43

Basic image plus ecosystem

6 of 43

Relation between individual and operator(s)

Social data handling operator

Financial data handling operator

Medical data handling operator

7 of 43

Ecosystem builds upon tf within legislation

Legislations

Trust frameworks (was there a point of possibly more TF’s)

8 of 43

Ecosystem

Operators responsibility towards the individual

Ecosystem level governance framework

Legislation

9 of 43

Reference model

Liability model

10 of 43

Governance

Logging and accountability

Identity management

Permission management

Service management

Data model management

Personal data storage

Value exchange

Personal data transfer

11 of 43

Image parts

12 of 43

MyData is about people, take Sarah

Sarah

13 of 43

Sarah has data in her Oura app - health and fitness data

Sarah

Oura

14 of 43

Sarah want to share that data to help solve the Corona crisis with the NHS

Sarah

Oura

NHS

15 of 43

How can Sarah be empowered to do so?

Sarah

Oura

NHS

?

16 of 43

Sarah needs infrastructure she can trust with her sensitive data...

Sarah

Oura

NHS

?

17 of 43

Oura and NHS can take care of that bilaterally, but....

Sarah

Oura

NHS

?

18 of 43

Oura and NHS can take care of that bilaterally, but how to...

Sarah

Oura

NHS

  • Find how/where the connection can be done?
  • Manage the permissions for the data to be exchanged?
  • Exchange the data itself?
  • Identifying Sarah, the NHS?
  • Check what Oura and NHS do with the data?
  • Update or add information?
  • Ensure the data is not changed?

19 of 43

.. and what if there are many sources, and many data using services involved?

Sarah

Oura

NHS

NHS

NHS

X

Z

2

3

20 of 43

Sarah needs to be facilitated in this

Sarah

Oura

NHS

NHS

NHS

X

Z

2

3

21 of 43

This is where the MyData operator comes in

Sarah

Oura

NHS

NHS

NHS

X

Z

2

3

22 of 43

An operator is <def>

Sarah

Oura

NHS

NHS

X

Z

2

3

23 of 43

Simplified

Person

Data source

Data using service

Operator

24 of 43

Simplified

Person

Data source

Data using service

Operator

25 of 43

There are many other important life events for Sarah. Buying a house, studying, relocating, …

Sarah is in a MyData ecosystem

Sarah

Oura

NHS

Tax �authority

Nordea

26 of 43

Simplified

Person

Data sources

Data using services

Ecosystem

Operators

27 of 43

Person

Data sources

Data using services

Ecosystem

Operators

Trust framework

Legislations

28 of 43

Additional slides Harri

29 of 43

Proto-operator: Permission management

Actuating new

permissions

Validating

permissions

Data transfer under valid permission

30 of 43

Proto-operator: PDS

Actuating transfer inbound

Data transfer to/from PDS-operator under valid permission

Actuating transfer outbound

31 of 43

Proto-operator: Identity manager

Acquiring ID

credentials

Issuance of credentials

Requesting ID proofs

Providing

ID proofs

32 of 43

Interoperability by level and type

Permissions Management

Transfer &

Data Model

Transactions Management

Permissions Roaming, Transactions Management & Data Transfer

Permissions, ID (& PDS) Portability

Increase in

complexity?

33 of 43

Interoperability Across Trust Framework Boundaries

Permissions, ID (& PDS) Portability

Permissions Roaming, Data Transfer & Transaction Management

34 of 43

Sources

35 of 43

Operator

Data Source

Data Using Service

Person

36 of 43

Person

Basic role model MyData/ eco system - UNDISPUTED -except for

the arrows

Caution: roles vs. entities!

Model as shown in 2018 Finnish-only paper

37 of 43

Reference model Digital We/discussion paper - applied to number of proto-operators (high-level and detailed)

  • Well-defined and validated
  • Should include value exchange as well
  • Too detailed for some of the discussions
  • How significant are the relative positions?

38 of 43

Finnish MyData infrastructure paper / Cities & Mydata:

  • Simplified structure
  • Includes semantics
  • Technology oriented, with business implications/functional aspects

39 of 43

IHAN blueprint 2.5:

  • Similar roles, similar layering
  • Very specific functionality / architectural choices
  • Nothing on trust network / governance

40 of 43

Towards a conclusion

  • The role model is a first level
  • Eventually, technological choices should be visualised / pointed to
  • Missing levels: business and functional (descriptive).
  • In terms of enterprise architecture: should describe business layer and link to application layer
  • Functionality is a ecosystem level
  • Governance, value exchange, semantics should be included

41 of 43

Synergy model

Governance

Logging and accountability

Identity management

Consent & permissions

Service management

Data model management

Personal data transfer and/or storage

Value transfer

Who I am and what is allowed?

Who is in the ecosystem my operator works with? And under what conditions?

How do we share and how do we understand each other?

Make it right - governance & accountability

Who is playing and what are the rules? Who is in charge?

What are we trying to do? Purpose

How do we do it? How do we organize our decisionmaking

42 of 43

Building Blocks

  • Governance:
  • Logging & accountability
  • t.b.d.

43 of 43

The MyData

Operator

‘bus’