Commit 7e25ade8 authored by Oskar van Deventer's avatar Oskar van Deventer Committed by fmerg

Replace correct links

parent afe7b3fe
# Template for Deliverable for the Pruductisation meeting of Data as Currency
<!--GENERAL ADVISE: Try to be brief, to the point, and concrete in your descriptions. Appropriately refer/link to your own work and/or that of others. -->
Contact person details: Petri Seljavaara
petri.seljavaara@wellbeingcart.com
## Business Page
### 1. Define your product
The Data as Currency (DaC) is an open source technical solution to value data through its lifecycle, by taking advantage of an invention called Overlays Capture Architecture (OCA). We will commercialize the DaC value by offering proprietary exchange wallet for consumers.
Corporates buy and sell data sets even today, but in our DaC model the value creation of data begins when there is a consent to use that data given by an individual using SSI, proper blinding protocol and the OCA schema.
DaC enables a multiplier overlay to be linked to a schema base giving a value proposition to attributes contained in the issued schema. As data is entered into the issued schema, the proposed values can then be translated into points to indicate the initial value of the data. Within the data lifecycle, value points can be added or subtracted whenever notice and consent requirements are pushed to the data principal. These recalculations will be dependent on any new multiplier overlays that have entered the data lifecycle since the previous calculation.
In the first implementation of DaC, the initial multiplier overlay will give a generic value proposition. Points can then be calculated according to the quality of the captured data. The SSI component allows the value propositions (i.e. multiplier overlays) to be auditable through the verifiable characteristics of VC technology and the assurance of issuance that that brings.
In our vision, the value points generated by the data flows can become an alternative to fiat currencies bringing a new value proposition to data and, ultimately, a preferred method of value. In this vision we offer the leading exchange wallet for consumers.
### 2. Value proposition – what is/are the benefit(s) for your customer
Data as Currency makes it appealing for corporates to apply SSI into the business they do today when selling data sets. Data as Currency creates the mechanism to gain profits by selling data that has consent captured by OCA.
In the first phase, DaC will indicate the quality of the captured data to the owner, seller and buyer as a basis for a new marketplace. SSI capabilities will add cryptographic assurance and human accountability to the process.
The solution enables developers to create new services based on the value of data. The value of data can be driven through multiplier overlays introduced during the data lifecycle. The value points associated with transferred data (i.e. DaC) can generate added-value services and data auction services through data quality assertions.
In our vision DaC and our exchange will be a more reliable method of transactions than fiat currencies.
### 3. Who are your customers
We have strong connections within the healthcare, pharmaceutical and food retail industries in Finland and envisage that the first production-ready DaC implementation will be a joint venture involving partners from those sectors.
The first phase will enable individuals and organizations to utilize DaC as an additional open source component within a dynamic data economy. The characteristics offered by SSI will be key to ensuring that the value of data can be audited throughout the data lifecycle.
In our vision our exchange will be the preferred place for transaction.
### 4. What is your targeted time to market (for a product on the market)
The DaC implementation and exchange will be developed as an eSSIF-Lab project from Q3/Q4 2020 to Q1 2021. Beyond that time frame, we will deploy the first pilot with our partners in Finland working with public data, health data and grocery behaviour data.
### 5. What is the business model
In the onboarding stage we charge our clients monthly subscription fees for DaC exchange and live project implementations.
In addition to DaC Wellbeing Cart will be providing commercial accelerator programs and technical implementation projects in all areas of decentralized data economy by using existing open source components. The goal is to steer the development towards an ecosystem where DaC is in the center.
Step by step we move towards a full featured exchange where users will be able to transform DaC points to other measures of value (e.g. fiat currency, tokens, key customer points, goods and services) and storing them in dedicated DaC-compliant wallets. In our vision, once the new data economy has matured, our sole business model will be a commission on DaC transactions.
### 6. Who will be your first customer (do you have a first customer?)
Our first customer will be a city in Finland that is creating a care path for its citizens and one of the leading market chains in Finland with whom we will be creating an alternative healthy food basket.
### 7. Do you plan to raise funds through private investors ?
Yes.
### 8. Have you already initiated contact with Venture Capital firms ?
Yes, we have direct access to seed investors in Finland. We are also interested in connecting with non-Finnish Venture Capital firms but, at the time of writing, have not investigated that avenue of funding yet.
## Technical Page
<!-- While creating contents for the following sections, please try to keep this section limited to a single page-->
### Please provide answers to the following questions before the productisation meeting:
1. What is the status of your product development?
TRL 2 – technology concept formulated
2. Are you aware of the eSSIF-Lab Library? What are the functionalities you would like to use?
We have studied the eSSIF-Lab architecture through the published web pages but noticed that the Library is not yet operational and that GitHub access has yet to be granted. The core DaC components will be open source. We are fully committed to sharing those components with other members of the community. We are also keen to integrate the components with those provided by the other eSSIF-Lab participants for the benefit of their projects.
### To be discussed duing the productisation meeting:
1. eSSIF-Lab partnerships: (see matchmaking process)
1. what do you have on offer to other participants ?
* A method to attach a value to the data (OCA compatible) and technology which enable value exchange in decentralized ecosystems.
* Components to integrated monetization layer into digital wallets (aka TDA)
* Components to integrated for data operators to create marketplaces for data
2. what would you like other participants to offer you ?
* Expertise in their fields
* Use cases
* Validation of our solution
2. How does your product fit within the eSSIF-Lab vision and architecture ?
We are introducing a monetization layer for data flows for SSI and consent driven data economy.
3. What is the timeline for the technical development ? Respect the milestones/timing… define the KPIs.
* Q3 2020 - Define the data capture and the SSI integration value - KPI -> overlay method ready
* Q4 2020 - Define the exchange and choose wallet - KPI -> exchange platform ready
* Q2 2021 - Integrate with any data operator for example with the Human Colossus´ Dynamic Data Sharing Hub - KPI -> proof of concept with first customers ready.
# Template for Deliverable for the Pruductisation meeting of Dynamic Data Sharing Hub
<!--GENERAL ADVISE: Try to be brief, to the point, and concrete in your descriptions. Appropriately refer/link to your own work and/or that of others. -->
Contact person details:
Dr.Philippe Page
Email: philippe.page@humancolossus.org
## Business Page
<!-- While creating contents for the following sections, please try to keep this section limited to a single page-->
### 1. Define your product
A Dynamic Data Sharing Hub designed with decentralisation, privacy and consent at its core. It starts with a Data Capture Hub (DCH) that ensures harmonised data at the source. Then Data Sharing Hubs (DSH) sitting with stakeholders of the ecosystem allows 3rd party requests to multiple source. (SEE [SUB-GRANTEE TECHNICAL SUMMARY](project-summary.md))
### 2. Value proposition – what is/are the benefit(s) for your customer
* Speed up onboarding in clinical trials through multi-source data searches respecting privacy and consent. Open doors to coordination between competing organisations
* Reduce complexity, cost and liability risks toward data protection regulations
### 3. Who are your customers
Early adopters will be a pharmaceutical company or a consortium of pharmas, medical and academic organisations. eSSIF-Lab project is designed to open the Dynamic Data Sharing concept to any industry in any domain.
### 4. What is your targeted time to market (for a product on the market)
Two years for large scale product:
* 2020 - development:
* OCA - Overlay Capture Architecture
* TDA - Trusted Digital Assistant
* DCH - Data Capture Hub
* DSH - Data Sharing Hub
* 2021:
* Data Sharing Hub first commercial integration.
* 2022:
* Ecosystem development.
### 5. What is the business model
The Human Colossus Foundation builds the generic Open Source components required for the data sharing hub. The foundation is not-for-profit funded by grants and earmarked donations (project funding) toward specific programs. HCF builds the components and then we will spin up a commercial company to deploy the services to customers (eg. pharmaceutical companies or any other large organisations).
### 6. Who will be your first customer (do you have a first customer?)
We have an existing pipeline and are already introducing SSI concepts by working with large pharmaceuticals on specific projects
### 7. Do you plan to raise funds through private investors ?
Yes. Project will be proposed to private firms as a product or as a joint venture investment.
### 8. Have you already initiated contact with Venture Capital firms ?
No, our project has a longer time horizon that do not fit usual VC firms short term gains.
## Technical Page
<!-- While creating contents for the following sections, please try to keep this section limited to a single page-->
### Please provide answers to the following questions before the productisation meeting:
1. What is the status of your product development?
Proof of Concept.
We are currently building core components which would allow us to test our concept of the Dynamic Data Sharing Hub with our partners. At the same time, sharing core components with the community and eSSIF-Lab members for the benefit of the whole ecosystem. This gives us a short feedback loop which gives us confidence in the build architecture. At the same time, it will also enable us to improve and validate core assumptions.
2. Are you aware of the eSSIF-Lab Library? What are the functionalities you would like to use?
We have looked at the eSSIF-Lab architecture through the web pages but understand that the Library is not yet operational and GitHub access just being granted. The Human Colossus Foundation is totally open source thus we look forward to share components and link with the ones provided by the other participants.
### To be discussed duing the productisation meeting:
1. eSSIF-Lab partnerships: (see matchmaking process)
1. what do you have on offer to other participants ?
* OCA
* SSI expertise
* Big vision where SSI is just one of the component
* Core components which help with rollout
2. what would you like other participants to offer you ?
* Expertise in their fields
* Use cases
* Validation of our assumptions
2. How does your product fit within the eSSIF-Lab vision and architecture ?
Our product is a natural extension of SSI allowing safe data sharing capabilities for other components.
3. What is the timeline for the technical development ? Respect the milestones/timing… define the KPIs.
3.1 {Régis} Competition analysis:
3.1.1 Perform an in-depth competition analysis centered on the Parmaceutical use case. Including:
- analysis of companies which address a similar challenges: “patient data ownership in clinical trials”,
- exploiting this concept centred onto the Pharma companies.
The analysis must give a list of potential competitors with the following minimal information: - Company name/Location/Size
- Maturity: date of inception, investment (Venture Capital ?) product readiness, customer reference ?
- Product: Identify their business model.
3.1.2 Strategic positioning: Propose a strategic mapping including the exploitation strategy.
3.2 {Régis} Refine the exploitation strategy beyond the eSSIF-Lab project:
3.2.1 Joint venture v.s. Service Company;
3.2.2 Propose a business model for the exploitation of the eSSIF-Lab development;
3.2.3 Give indications of the financial sustainability of the future entity.
3.3 {Rieks} Overview of components already available, in particular with other eSSIF-Lab participants
3.4 {Oskar} Detail how the use of OCA advances a Unified Data Language and how the Dynamic Data Sharing Hub will provide an example.
- Explain the business aspect of OCA
3.5 Timeline for the technical development. The self-imposed Human Colossus KPIs are:
* Q3 2020 - Sandbox environment with OCA and TDA - KPI -> showcasing data flow with consent
* Q4 2020 - Data Capture Hub and Data Sharing Hub KPI -> showcasing the choosen use cases in pharmaceutical industry
# BOC-1 - Project Summary of Dynamic Data Sharing Hub
For more information, please contact:
Dr. Philippe Page
Email: philippe.page@humancolossus.org
<!--Try to be brief, to the point, and concrete in your descriptions. Appropriately refer/link to your own work and/or that of others.
Be mindful of the audience you target, which include other eSSIF-Lab subgrantees, project experts that evaluate your work, and other audiences in the NGI-EU community. Make sure your texts help them understand how your work may benefit theirs, what you need of them, and how everything fits together-->
## Summary
The Human Colossus vision is "Data has values when it flows and it is costly when it stagnates". We articulate it through an architecture called "Dynamic Data Economy -DDE" made possible by the existence of Self-Sovereign Identity an advanced form of decentralised digital identity. Our [website](https://humancolossus.foundation) provides additional information and the following post ["Genesis of DDE"](https://humancolossus.foundation/blog/dde-first-contact), frames the economic problems we address.
Our eSSIF-lab project Dynamic Data Sharing Hub is born out of our experience in the pharmaceutical arena where the exchange of complex and sensitive data has driven complexity and costs to unprecedented level in clinical trials. With sensitive patient data involved, adding privacy is slowing down innovation, add costs and increase liability to most stakeholders through compliance requirements with the data protection regulations.
Our contribution is a Dynamic Data Sharing Hub designed with decentralisation, privacy and consent at its core. It starts with a Data Capture Hub (DCH) that ensures harmonised data can be shared. Then data can be shared across multiple stakeholders through a Data Sharing Hub ensuring a data entry with consent
Our Data Sharing Hub provides both the components for an SSI based data sharing flow that can be used within the eSSIF-Lab architecture as well as the realisation of a specific instance addressed to, but not limited to, the medical sector.
## Business Problem
The medical & pharmaceutical sector represents huge Data Harmonization challenges: Complex data set (e.g. clinical trials), Extremely sensitive data (e.g. patient data), Worldwide scale (e.g. internationalization challenges). Data Harmonization is the predominant factor to simplify and reduce cost of real-world source data transformation.
<!--Provide a *concise* description of the business problem you focus on. What is the problem? Who needs to deal with it/suffers drawbacks?-->
## (Technical) Solution
<!--Provide a *concise* list of the (concrete) results you will be providing (include a summary description of each of them), and how they (contribute to) solve the business problem(s)-->
* OCA tooling - Overlay Capture Architecture - layered architecture for describing data semantic, facilitating unify data language. Helping with data harmonization, data portability, data capture. The aim of the project is to provide basic tools and integration points to use OCA in existing and newly created systems. It would enable data flows between legacy systems and newly SSI, consent based ecosystems.
* Data Sharing Hub - set of components allowing to bootstrap own data sharing hub which would be able to collect, aggregate, and query data sets all driven by SSI and consent.
* Digital Wallet - User wallet which allows to control and manage data consent and identity.
* Data Vault - Data interfaces controlled by user to provide access and share data with the ecosystem.
* Assurance Netowkr - Indy based DLT network for identity
## Integration
<!--Provide a precise description of how your results will fit with the eSSIF-Lab functional architecture (or modifications you need). Also, provide descriptions of how your results (are meant to) work, or link together in a meaningful way, both within the eSSIF-Lab family of projects, within EU-NGI, with US-DHS-SVIP, cross-border and/or other.-->
OCA introduce interoperable schema which solves a lot of problems of SSI world and introduce unify data language to the eSSIF-Lab family and projects, enabling data flows. OCA solves some of the major issues of SSI space, just to name few:
* Interoperable VC,
* Internationalization of data,
* Data portability
In addition Data Sharing Hub would enable companies to build their business model on new form of data flows which enable to get access to richer data following proper consent and data protection rules.
## Core components
Dynamic Data Sharing Hub introduce set of core components which would show case how to take SSI into next level and start thinking of data flows instead of just identity and simple verifable information. All core components would be available as open source component and ready to be used by other memebrs of eSSIF-Lab. Stay tune!
## <!--Your own section(s)-->
<!--Include sections for other stuff you want other eSSIF-Lab subgrantees (including those that applied for other calls) to become aware of.-->
This diff is collapsed.
# BOC-1 - Project Summary of <!--subproject name-->
# BOC-1 - Project Summary of <!Data as Currency>
For more information, please contact:
......
# Template for Deliverable for the Pruductisation meeting of <!--your project>
# Template for Deliverable for the Productisation meeting of <!--your project>
<!--GENERAL ADVISE: Try to be brief, to the point, and concrete in your descriptions. Appropriately refer/link to your own work and/or that of others. -->
......@@ -12,12 +12,12 @@ Contact person details:
## PRODUCT PAGE
<!-- While creating contents for the following sections, please try to keep this section limited to a single page-->
### 1. Define your product
### 1. Define your product component(s)
The purpose of this section is to give readers a good idea of what you will be providing, so that they determine what you will be providing and whether or not that addresses their needs. So for each component that you will be providing, state:
- its name (so that we may refer to it)
- its function (one or two lines, and if possible, use the functions as defined in the eSSIF-Lab functional architecture)
- for every API the component provides:
- for every interface (API, protocol, ...) the component provides:
- its name
- its function
- any functionality that the component needs (to be provided by other components, which you or others may provide).
......@@ -48,8 +48,8 @@ The purpose of this section is to give readers an idea of the possibilities and
### 5. Demo
State the kind(s) of demo's that you will be providing and/or participating in to show that the interop as specified in the previous section actually works.
### 6. eSSIF-Lab Vision, Architecture, Terminology, APIs, and further Documentation
At the end of the project, a vision, architecture, terminology, APIs and other documentation should exist that results from a collaboration of the subgrantees and the project team. Currently, there is a draft vision and functional architecture that gives the readers a high-level idea of what the eSSIF-Lab infrastructure is about, and how it can be used in a business. Also, some terminology has been provisionally defined. There is little API and further documentation.
### 6. eSSIF-Lab Vision, Architecture, Terminology, interfaces, and further Documentation
At the end of the project, a vision, architecture, terminology, interfaces (APIs, protocols, ...) and other documentation should exist that results from a collaboration of the subgrantees and the project team. Currently, there is a draft vision and functional architecture that gives the readers a high-level idea of what the eSSIF-Lab infrastructure is about, and how it can be used in a business. Also, some terminology has been provisionally defined. There is little API and further documentation.
In order for this overall project deliverable to be delivered, state:
- what you think is needed (short, to the point)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment